GB2339940A

GB2339940A - Data processor data processing method and data processing system

Info

Publication number: GB2339940A
Application number: GB9924381A
Authority: GB
Inventors: Masayuki Taniguchi; Mayumi Ojima; Atsushi Mase; Kazuhiro Iwamoto; Haruki Kawamura; Toshihiko Ogiso; Kentarou Morikami
Original assignee: Mitsubishi Electric Corp
Current assignee: Mitsubishi Electric Corp
Priority date: 1997-04-14
Filing date: 1997-04-14
Publication date: 2000-02-09
Anticipated expiration: 2017-04-14
Also published as: GB2339940B; WO1998047073A1; DE19782267T1; HK1025410A1; GB9924381D0

Description

2339940 COPY PATENT OFFICE - DERNITIVz

SPECIFICATION-

METHOD AMD APPARATUS FOR PROCESSING DATA, AND DATA PROCESSING SYSTEM Field of the Invention

The present invention relates to a method and apparatus for processing data and a data pr.ocessing systemo wherein data are collected from or set on a device which is an object of control, by way of a communications line.

Background

FIG. 34 is a block diagram showing the configuration of a conventional data processor. In the drawing, reference numeral 200 designates a controller for controlling a CRT 2 and a keyboard 3, which together serve as an 1/0 device, and a plurality of programmable logic controllers (PLC) 4 connected to respective communications lines 5, which are compliant with different communications protocols.

The following description is based on the assumption that three communications lines (communications lines 5a, 5b, and 5c) are provided so as to correspond to the respective PLCs 4 (PLC 4a, PLC 4b, and PLC 4c).

The controller 200 comprises a CPU 210 which executes a user program 221, such as a PLC device data collection/setting program, which is expanded in memory 220; an interface 231 with the CRT 2; an interface 232 with, for example the keyboard 3; and interfaces 241, 242, and 243 with the PLCs 4a, 4b, and 4c connected to the communications lines which are compliant with different communications protocols.

FIG. 35 shows the statuses of the memories of the PLCs I 4a, 4b, and 4c. In the drawing, 40 designates the memories of the respective PLCs 4, and 41 designates device data stored in the memories.

The PLCs 4a, 4b, and 4c are provided with memories 40a, 40b, and 40c, respectively. The memories 40a, 40b, and 40c store device data 41a, 41b, and 41c, respectively.

FIG. 36 shows a flowchart for collecting data from the PLCs 4 connected to the conventional different communications lines. The flowchart shows the operation of the user program 221 when data are collected in the following sequence; that is, devices WO to W99, representing the product number relating toa device region 41a, from the memory 40a of the PLC 4a; devices DO to D49, representing number-of-finished-products data relating to a device region 41b, from the memory 40b of the PLC 4b; and devices R10 to 20, representing measurement data relating to a device region 41c, from the memory 40c the PLC 4c.

FIG. 37 is a flowchart for setting data on the PLCs 4 connected to the conventional different communications lines. This flowchart shows the operation of the user program when data are set in the following sequence; that is, devices WO to W99, representing the product number relating to the device region 41a of the memory 40a of the PLC 4a; devices DO to D49, representing number-of-finished-products data relating to the device region 41b of the memory 40b of the PLC 4b; and devices R10 to 20, representing measurement data relating to the memory 40c of the device region 41c of the PLC 4c.

A conventional data collection method will be described by reference to FIGS. 34 to 36.

This conventional example will describe a case where 2 according to the user's wishes, there are collected data relating to devices WO to W99, which are product number data, from the PLC 4a; data relating to devices DO to D49, which are number-of-finished-products data, from the PLC 4b; and data relating to the devices R10 to 20, which are measurement data, from the PLC 4c.

First, an explanation will be given of collection of the devices WO to W99, representing product number data, from the PLC4a.

In step S1601, the user sets, as a user program, a communications protocol which the controller 200 uses to establish communication with the PLC 4a, designates device data (devices WO to W99 representing product number data) to be collected f rom the PLC 4a, -and prepares communication data, such as data about a user buffer in which the collected device data are to be collected and data about collection timing. Processing then proceeds to step S1602.

In step S1602, the communications line 5a is opened in accordance with the communications protocol assigned to the PLC 4a on the basis of the thus-prepared communication data. Processing then proceeds to step S1603.

In step S1603, devices WO to W99, which are product number data, are actually collected from the PLC 4a, and the thuscollected data are stored in a designated user buffer.

After completion of collection of the data, in step S1604 the communications line 5a is closed in accordance with the communications protocol assigned to the PLC 4a on the basis of the communication data.

As mentioned above, devices WO to W99, which are product number data, are collected from the PLC 4a.

3 Subsequently, in step S1605, a determination is made as to whether or not collection of all the device data sets has been completed. In this case, collection of the number-offinished-products data from the PLC 4b and collection of the measurement value data from the PLC 4c have not yet been completed. Processing returns to step S1601 in order to collect number-of-finished-products data. In steps 1601 to 1604, number-offinished-products data D1 to D49 are collected.

Similarly, measurement data R10 to R20 are collected from the PLC 4c, whereby collection of all the device data sets is completed. Processing then proceeds to step S1606.

In step S1606, a determination is made as to whether or not a round of data collection operations has been completed. In a case whether device data have been consecutively collected to the PLC, processing proceeds to step S1607, where, for example, an arbitrary scan timing is awaited. At the next scan timing; that is, at the next data collection timing, data are collected from the PLCs 4a, 4b, and 4c.

The arbitrary timing corresponds to a given time interval or variations in the contents of the data relating to the PLC.

If in step S1606 completion conditions are satisfied, a round of operations for collecting device data from the PLCs have been completed.

A conventional data setting method will now be described by reference to FIGS. 34, 35, and 37.

This conventional example will describe a case where, according to the user's wishes, there are collected data relating to devices WO to W99, which are product number data, from the PLC 4a; data relating to devices DO to D49, which are number-of-finished-products data, from the PLC 4b; and data 4 relating to the devices R10 to 20, which are measurement data, from the PLC 4c.

In step S1701, the user sets, as a user program, a communications protocol which the controller 200 uses to establish communication with the PLC 4a, designates a user buffer which stores data set on the PLC 4a and device data (devices WO to W99 representing product number data) to be set on the PLC 4a, and through use of the user program, preparescommunication data, such as setting timing. Processing then proceeds to step S1702.

In step S1702, the communications line 5a is opened in accordance with the communications protocol assigned to the PLC 4a on the basis of the thus-prepared communication data.

Processing then proceeds to step S1703.

In step S1703, devices WO to W99, which are product number data, are actually set on the PLC 4a from the designated user buffer.

After completion of setting of the data, in step S1704 the communications line 5a is closed in accordance with the communications protocol assigned to the PLC 4a.

As mentioned above, devices WO to W99, which are product number data, are set on the PLC 4a.

Subsequently, in step S1705, a determination is made as to whether or not setting of all the device data sets has been completed. In this case, setting the number-of-finished- products data on the PLC 4b and setting the measurement value data on the PLC 4c have not yet been completed. Processing - returns to step S1701 in order to set number-of-finishedproducts data on the PLC 4b. In steps 1701 to 1704, number-of-finished-products data Dl to D49 are set.

Similarly, measurement data R10 to R20 are set on the PLC 4c, whereby setting of all the device data sets is completed. Processing then proceeds to step S1706.

In step S1706, a determination is made as to whether or not a round of data setting operations has been completed. In a case when device data have been consecutively set on the PLCs, processing proceeds to step S1707, where, for example, an arbitrary scan timing is awaited. At the next scan timing; t-hat-is, at the next data setting timing, data are set on the PLCs 4a, 4b, and 4c.

If in step S1706 completion conditions are satisfied, a round of operations for setting device data on the PLCs has been completed.

Another conventional example will now be described by reference to FIGs. 38 and 39.

FIG. 38 is a block diagram showing the configuration of a conventional data collection device equipped with two controllers.

In the drawing, the data collection device is provided with two controllers 200 and 201. The controllers 200 and 201 are connected together by way of protocol E interfaces 245 by way of a single communications line 5e.

The controller 200 is connected to the PLC 4a by way of a protocol A interface 241 and the communications line 5a, and the controller 201 is connected to the PLC 4d by way of a protocol 6 D interface 234 and a communications line 5d.

The controller 200 collects or sets data in accordance with the user program 221 stored in the memory 220.

In other respects, the present conventional example is identical in configuration to the previous conventional example, and hence repetition of its explanation is omitted here.

The controller 201 incorporates the CPU 210, the memory 220, the user program 221, the I/F 231 with the CRT, and the I/F 232 with the keyboard, so as to correspond to the CPU 210, the memory 220, the user program 221, the I/F 231, and the I/F 232 incorporated in the controller 200.

FIG. 39 shows a flowchart for the user program relating to a method of collecting and transporting data between the controllers 200 and 201 connected together by way of the communications line 5e. For example, the flowchart shows a round of processing operations (user program) relating to setting (transporting) of data W100 to W199, which are product number data pertaining to the device region formed in the PLC 4d connected to the controller 201, as data WO to W99 in the device region of the PLC 4a connected to the controller 200. In this case, the communications protocol used by the PLC 4a connected to the controller 200 differs from that used by the PLC 4d connected to the controller 201.

In step S1801, the user sets, as a user program, communication data which the controller 201 uses to establish communication with the PLC 4d; that is, a communications protocol which the controller 201 uses to establish communication with the PLC 4d, designates device data (devices W100 to W199 representing product number data) to be collected from the PLC 4d, and prepares communication data, such as data 7 about a user buffer of the controller 201 in which the collected device data are to be collected and data about collection timing.

Further, the user sets communication data which the controller 200 uses to establish communication with the PLC 4a; that is, a communications protocol which the controller 200 uses to establish communication with the PLC 4a, designates a user buffer which stores data to be set on the PLC 4a and device data (devices WO to W99 representing product number data) to be set on the PLC 4a, and prepares communication data, such as setting timing.

Processing then proceeds to step S1802.

In step S1802, the communications line Se is opened in accordance with the communications protocol assigned to the controllers 200 and 201, and processing then proceeds to step S1803.

In step S1803, by way of the thus-opened communications line 5e, there are transmitted a request for collecting data relating to devices WO to W99, which are product number data pertaining to the PLC 4d, from the controller 201 to the controller 200, and communications data which are prepared in step S180 and are used by the controller 201 to establish communication with the PLC 4d. Processing then proceeds to step S1804.

In step S1804, on the basis of the communications data transmitted from the controller 200, the communications line 5d is opened in accordance with the communications protocol used between the controller 201 and the PLC 4d, and processing then proceeds to step S1805.

In step S1805, data relating to devices W100 to W199, 8 which are product number data, are actually collected from the PLC 4d. The thus-collected data are temporarily stored in the memory 220 provided within the controller 201, and processing then proceeds to step S1806.

In step S1806, through communication established between the controllers 200 and 201, the data relating to the devices W100 to W199 stored in the memory 220 provided within the controller 201 are transported to the memory 220 provided within the controller 200. Processing then proceeds to step S1807.

In S1807, the communications line 5d, which is open, is closed in accordance with the communications protocol used between the controller 201 and the PLC 4d. Processing then proceeds to step S18.08.

In step S1808, the communications line 5e, which is open, is closed in accordance with the communications protocol assigned to the controllers 200 and 201.

Collection of data pertaining to devices W100 to W199, which are product number data, from the PLC 4d is now completed.

Next, processing enters a flow for setting data pertaining to devices W100 to W199, which are product number data stored in the memory 220 provided within the controller 200, on the PLC 4a connected to the controller 200.

In step S1809, the communications line 5a is opened in accordance with the communications protocol assigned to the PLC 4a, and processing then proceeds to step S1810.

In step S1810, communication is established between the controller 200 and the PLC 4a. Data pertaining to devices W100 to W199, which are product number data stored in the memory 220 provided within the controller 200, are stored in the device region 41a within the PLC 4a, whereby the data are taken as 9 devices WO to W99. After completion of data setting, in step S1811 the communications line 5a is closed in accordance with the communications protocol assigned to the PLC 4a. Transportation of a series of product number data sets stored in the PLC 4d connected to the controller 201 to the PLC 4a connected to the controller 200 by way of the communications line is now completed.

As mentioned above, under the conventional data collect ion/setting method, in a case where a plurality of PLCs are connected to controllers by way of different communications protocols or communications lines, in order to enable the controller to collect data from or set data on the respective PLCs, communication data must be prepared through use of the user program in accordance with designated communications protocols which correspond to the respective PLCs and are used for establishing communication with the respective PLCs. Preparation of the communication data requires expert knowledge about communications protocols. Communications data relating to opening or closing of a communication line according to the respective different communications protocols are prepared, thus disadvantageously bloating the program and degrading the performance of the program.

The method of collecting data f rom or setting data on PLCs connected to controllers, which are connected together by way of communications lines, requires accessing memory provided in the PLCs, capturing data into the memories of the controllers, and performing data collection or setting operations for another controller differing from the controller from which the data are collected or a PLC connected to another controller. As in the case of the foregoing problems, the user program for data collection and setting purposes becomes complicated and bloated. Further, there must also be prepared a user program only for accessing the memory of the PLCs connected to the controllers.

A lot of overhead communications time is required for consecutive operation, in which a user program is repeatedly performed, resulting in degradation in performance of the program.

Intervals at which data are collected from a PLC connected to a controller are set by the user program. In order to change the intervals at which the device data are collected, the entireuser program must be changed. A great amount of labor is required for arbitrarily changing the intervals at which device data are collected from the controller.

Refresh parameter data, which are used for refreshing data to be collected or set at all times and are stored in a refresh parameter storage area of each of the controllers, must be set by means of identical setting operations through use of the corresponding user programs, thus degrading workability and imposing a great burden on the user.

Summa=y of the Invention The present invention has been conceived to solve the foregoing problems, and the object of the present invention is to provide a method and apparatus for processing data and a data processing system, which enable easy execution of data processing required between a controller and a PLC connected to the controller without involvement of preparation of a complicated and sophisticated user program.

Another object of the present invention is to provide a data processing method and apparatus which enables connection of a plurality of controllers and data processing required among the controllers without involvement of preparation of a complicated and sophisticated user program.

Still another object of the present invention is to provide a data processing method and apparatus which improves the efficiency of data setting, such as setting of parameters.

To these ends, according to one aspect of the invention, there is provided a data processorcomprising:

communications protocol storage means for storing beforehand, in a device to be controlled, a communications protocol assigned to the device connected to the data processor by way of a communications line; device data processing means for collecting device data of the device or setting device data on the device in accordance with the communications protocol stored in the communications protocol storage means; a shared memory location for storing the device data collected by the device data processing means or the device data to be set on the device; and data exchange means for exchanging the device data between the shared memory location and a designated user buf f er.

Particularly, the device data processing means preferably has a refresh control function for collecting device data of the device or setting device data on the device at predetermined timing.

Particularly, the device data processing means reads, as a parameter and from a setting data file in which data are set, a predetermined timing at which refresh control is effected.

Particularly, the data exchange means exchanges all the 12 data sets-between the shared memory location and the designated user buffer through use of communications means, which has been standardized and set beforehand.

Particularly, the data exchange means exchanges device data between the shared memory location and the user buffer every time the value of the device data is changed.

Particularly, the shared memory location is divided into blocks and each block stores device data pertaining to the corresponding device to be controlled.

According to another aspect of the present invention, there is also provided a data processing method, comprising thesteps of:

reading, from communications protocol storage means in which protocols are stored beforehand for each device to.be controlled, a communications protocol assigned to a device which is an object of control and is connected by way of a communications line; collecting device data of the device or setting device data on the device by way of the communications line according to the communication protocol that is read; storing, in a shared memory location, the device data collected from the device or the device data set on the device; and exchanging the device data between the shared memory location and a designated user buffer.

Particularly, the step of storing, in the shared memory location, the device data collected from the device or the device data set on the device is effected at a preset timing.

According to yet another aspect of the present invention, there is provided a data processing system, wherein a plurality 13 of controllers, each being connected to a device to be controlled by way of a first communications line, are connected together by way of a second communications line, wherein the controller comprises device data processing means which collects device data from the device or sets device data on the device in accordance with a communications protocol assigned to the first communications line; a shared memory location which stores the device data collected from the device by the device data processing means or the device data to be set on the device; data exchange means for exchanging the device data between the shared memory location and a designated user buf f er; second communications protocol storage means for storing in advance a communications protocol assigned to the second communications line; transmission means for transmitting the device data stored in the shared memory location over the second communications line in accordance with the communications protocol assigned to the second communications line, the device data being stored in the second communications protocol storage means; and write means for storing the device data transmitted over the second communications line into the shared memory location.

Particularly, the data processing system further comprises first communications protocol storage means for storing, in advance and for each device, a first communications protocol used for establishing communication with the devices to be controlled, which are connected to the controllers by way of the first communications line.

III Particularly, the device data processing means has a refresh control function for sequentially collecting data from the devices to be controlled or setting data on the devices to be controlled, at a predetermined timing.

Particularly, the transmission means transmits the device data at a predetermined timing over the second communications line, on the basis of the parameters stored in the shared memory location.

Further, the transmission means operates at uniform intervals, the length of which is transmitted from activation means which operates on the basis of a predetermined paramet-er.- Particularly, write means stores.the device data transmitted over the second communications line into blocks into which the shared memory location is divided so as to correspond to the respective devices.

Particularly, the second communications line corresponds to Ethernet protocol.

Particularly, the parameters stored in the shared memory location are transmitted over the second communications line.

Further, a determination is made as to whether the data transmitted over the second communications line are parameters or device data. If the data correspond to parameters, the parameters are stored in a parameter storage area of the shared memory location. If the data correspond to device data, the device data are stored in a storage area assigned to the respective devices to be controlled.

B-r-ief Description of the Drawings

FIG. 1 is a block diagram showing the configuration of a data collection device according to a first embodiment of the present invention; FIG. 2 is a functional diagram showing the functions of the data collection device according to the first embodiment; FIG. 3 is a flowchart showing the operation of shared memory data collection means provided within data collection means according to the first embodiment; FIG. 4 is a flowchart showing the operation of device data collection means provided within the data collection means according to the first embodiment when the device data collection means collects data from PLCs; FIG. 5 is a diagram showing the configuration of shared memory and contents stored in the same according to the first embodiment; FIG. 6 is a block diagram showing the configuration of a data setting device according to a second embodiment of the present invention; FIG. 7 is a functional diagram showing the functions of data setting means according to the second embodiment; FIG. 8 is a flowchart showing the operation of shared memory data setting means provided within the data setting means according to the second embodiment; FIG. 9 is a flowchart showing the operation of device data setting means provided within the data setting means according to the second embodiment when the device data setting means sets data on a PLC; FIG. 10 is a diagram showing the configuration of shared memory and contents stored in the same according to the second embodiment; FIG. 11 is a block diagram showing the configuration of a refresh-type data collection device according to a third 16 embodiment of the present invention; FIG. 12 is a functional diagram showing the functions of the refresh-type data collection means according to the third embodiment; FIG. 13 is a flowchart showing the operation of shared memory data collection means provided within the refresh-type data collection means according to the third embodiment; FIG. 14 is a flowchart showing the operation of device data collection refresh means provided within the refresh-type data setting means according to the third embodiment when the device data setting means collects data from a PLC; FIG. 15 is a block diagram showing the configuration of a refresh-type data setting device according to a fourth embodiment of the present invention; FIG. 16 is a functional diagram showing the functions of the refresh-type data setting means according to the fourth embodiment; FIG. 17 is a flowchart showing the operation of shared memory data setting means provided within the ref resh-type data setting means according to the fourth embodiment; FIG. 18 is a flowchart showing the operation of device data setting refresh means provided within the refresh-type data setting means according to the fourth embodiment when the device data setting refresh means sets data on a PLC; FIG. 19 is a block diagram showing the functions of a data collection device according to a fifth embodiment; FIG. 20 is a functional diagram showing the functions of data collection means according to the fifth embodiment; FIG. 21 is a flowchart showing the operations of protocol A device data collection means, the operations of protocol B 17 device data collection means, and the operations of protocol C device data collection means according to the fifth embodiment; FIG. 22 is a table showing files of data base format in an auxiliary storage device for storing data which set intervals at which device data are collected from a PLC according to the fifth embodiment; FIG. 23 is a block diagram showing the configuration of a data collection device according to a sixth embodiment of the present invention; FIG. 24 is a functional diagram showing the functions ofthe data collection means according to the sixth embodiment; FIG. 25 is a table showing the details of device refresh parameters set by the user on shared memory according to the sixth embodiment; FIG. 26 is a table showing one example of contents of device write request transmission data to be transported to another controller according to the sixth embodiment;FIG. 27 is a flowchart showing the operation of means for activating write request transmission means which requests device data of one controller to be transmitted to another controller at predetermined timing according to the refresh parameter according to the sixth embodiment; FIG. 28 is a flowchart showing the operation of the means for activating write request transmission means which requests device data of one controller to be transmitted to another controller at predetermined timing according to the refresh parameter according to the sixth embodiment; FIG. 29 is a flowchart showing the operation of means which receives a write request transmitted from another is controller and writes the request into shared memory according to the sixth embodiment; FIG. 30 is a functional diagram showing the functions of refresh parameter data setting means according to a seventh embodiment of the present invention; FIG. 31 is a flowchart showing the operation of means for transporting device refresh parameter data to another controller according to the seventh embodiment; FIG. 32 is a flowchart showing the operation of means for writing data transmitted from another controller on the shared memory according to the seventh embodiment; FIG. 33 is a flowchart showing the operation of a user program for setting device refresh parameter data on the shared memory according to the seventh embodiment; FIG. 34 is a block diagram showing the configuration of a conventional data collection device; FIG. 35 schematically shows the statuses of memories of PLCs 4a, 4b, and 4c; FIG. 36 is a flowchart for collecting data from PLCs 4 connected to a controller by way of conventional different communications lines; FIG. 37 is a flowchart for setting data on the PLCs 4 connected the controller by way of the conventional different communications lines; FIG. 38 is a block diagram showing the configuration of a conventional data collection device; and FIG. 39 is a flowchart of a user program, showing a method of collecting/transporting data between controllers 200 and 201 connected by way of a communications line 5e.

19 -Best Modes for Working the invention Embodiments of the present invention will now be described. First Embodiment A first embodiment of the present invention relating to a data collection method will now be described by reference to FIGS. 1 through 5.

FIG. 1 is a block diagram showing the configuration of a data collection device according to a first embodiment of the present invention. In the drawing, reference numeral 100 designates a controller for controlling a CRT 2 and a keyboard3, which together serve as an 1/0 device, and a plurality of programmable logic controllers (PLC) 4 (PLC 4a, PLC 4b, and PLC 4c) connected to the controller by way of respective different communications means. Reference numeral 110 designates a CPU for executing data collection means 122 or a user program 121, such as a PLC device data collection program, which is expanded in memory 120. Reference numeral 131 designates an interface with the CRT 2; 132 designates an interface with the keyboard 3; 141, 142, and 143 designate interfaces with the PLCs 4a, 4b, and 4c, which are connected to the controller by means of different communications protocols; and 5a, 5b, and 5c designate communications lines connected to the PLCs 4a, 4b, and 4c, which are connected to the controller by means of different communications protocols.

FIG. 2 is a functional diagram showing the functions of the data collection means 122 which operates within the memory 120 shown in FIG. 1. In the drawing, reference numeral 1221 designates a shared memory location for storing device data of the PLCs 4a, 4b, and 4c; 1222 designates data collection means which serves as data exchange means for exchanging device data between the shared memory location 1221 and a designated user buffer; 1223 designates device data collection means which acts as device data processing means and is equipped with communications protocol storage means for storing communications protocols assigned to the PLCs 4; 1223a designates device data collection means for use with the PLC 4a connected to the controller by means of protocol A; e.g., RS-232-C protocol; 1223b designates device data collection means for use with the PLC 4b connected to the controller by means of protocol B; e.g., Ethernet protocol; and 1223c designates device data collection means for use with the PLC 4c connected to the controller by means of protocol C; e.g., original LAN protocol.

FIG. 3 is a flowchart showing the operation of the shared memory data collection means 1222 provided within the data collection means 122. The flowchart shows the operation of the user program 121 and the operation of the shared memory data collection means 1222, wherein the user program 121 invokes the shared memory data collection means 1222, to thereby collect data from the PLCs 4a, 4b, and 4c connected to the controller by way of different communications lines in the following sequence; that is, devices WO to W99 representing the product number relating to the PLC 4a; devices DO to D49 representing number-of-finished-products data relating to the PLC 4b; and devices R10 to 20 representing measurement data relating to the PLC 4c.

FIG. 4 is a flowchart showing the operation of the device data collection means 1223 provided within the data collection means 122 when the device data collection means 1223 collects 21 data from the PLCs 4. Particularly, the flowchart shows the operation of protocol A device data collection means 1223a when the protocol A device data collection means collects data relating to devices WO to W99, which are product number data, from the PLC 4a.

FIG. 5 is a diagram showing the contents of the shared memory location 10The operation of the data collection device according to the first embodiment will now be described.

First, the outline of operation of the data collection device will be described by reference to FIG. 2.

A user (operator) designates, in an interactive manner, device data which the user desired to collect; that is, a PLC in which the desired device data are stored; a user buffer into which the thus-collected device data are stored; and a device data storage area on the shared memory location 1221.

As a result of designation of the PLC.by the user, the CPU 110 directs the device data collection means 1223a, 1223b, and 1223c to activate the PLC designated by the user.

In accordance with communications protocols stored in the respective device data collection means 1223a, 1223b, and 1223c, the device data collection means 1223a, 1223b, and 1223c actually establish communication with the PLCs 4a, 4b, and 4c, collect device data from the same, and store the thus-collected device data into the shared memory location 1221.

The shared memory data collection means 1222 stores into the user buffer designated by the user the device data relating to the PLCs 4a, 4b, and 4c, which are collected by the device data collection means 1223a, 1223b, and 1223c and stored in the shared memory location 1221.

22 In this way, the user can collect device data relating to a specific PLC by designation of only a PLC from which the user desires to collect device data, the user buffer for storing the thus-collected device data, and the device data storage area on the shared memory location 1221.

By reference to FIGS. 3 and 5, there will be described in detail operations of the data processor or operations of the data processor for collecting data; that is, collection of data pertaining to devices WO to W99, which represent the product number, from the PLC 4a; collection of data pertaining to devices DO to D4 9, which represent number-of -f inished-productsdata, from the PLC 4b; and data pertaining to devices R10 to 20, which represent measurement data, from the PLC 4c.

First, an explanation will be given of an operation required when the user himself writes a user program into memory.

The user prepares a user program for designating a PLC where device data to be collected are to be stored, a user buf f er where the thuscollected device data are to be stored, and a device data storage area on the shared memory location 1221. The thus-prepared user program is stored into the memory 120, and the processing to be performed by the user is now completed.

In the present embodiment, the.above-described operations required to be performed by the user correspond to operations for collecting data pertaining to devices WO to W99, which are product number data, from the PLC 4a; storing the thus-collected data into the user buffer; collecting data pertaining to devices R10 to 20, which are measurement data, from the PLC 4c; and storing the thus-collected data into an arbitrary user buffer. In other words, the user performs, three 23 times, the operations for designating a PLC where device data are stored; a user buffer into which the thus-collected device data are stored; and a device data storage area on the shared memory location 1221.

There will now be described the operation of the data collection means which are provided within the data collection device and operate according to the user program written by the user.

In step S101, according to the user program written by the user, devices WO to W99 representing product number data to be collected from the PLC 4a; a PLC-4a device data stor-agearea 1221a on the shared memory location 1221 where the device data collected from the PLC 4a are to be temporarily stored; and the user buffer into which the device data are to be finally stored, are directed to the shared memory data collection means 1222. The shared memory data collection means 1222 is invoked, and processing then proceeds to step S102.

In step S102, the shared memory data collection means 1222 selects a communications protocol used when communication is actually established with the PLC 4a; that is, the protocol-A device data collection means 1223a, from the communication protocols which are stored in advance so as to correspond to the respective PLCs connected to the controller 100 - The device data desired to be collected from the PLC 4a, and the PLC 4a device data storage area 1221a on the shared memory where the device data collected from the PLC 4a are to be temporarily stored, are directed to the protocol-A device data collection means 1223a. The protocol-A device data collection means 1223a is activated, to thereby temporarily store the device data stored in the PLC 4a; that is, the product number data, into 24 the shared memory 1221 (the operation of the protocol-A device data collection means 1223a will be described later). Processing then proceeds to step S103.

In step S103, the data pertaining to devices WO to W99, which represent product number data and are stored by means of the protocol-A device data collection means 1223a, are transported from the PLC-4a device data storage area 1221a in the shared memory 1221 to the user buffer specified by the user in accordance with the user program.

A round of operations required for storing the data pertaining to devices WO to W99, which are the product number. data collected f rom the PLC 4 a, into the user buf f er designated by the user are now completed through the processing relating to steps S101 to S103.

In step S104, in order to collect, from the PLC 4b, data pertaining to devices DO to D49 representing number-offinished-products data, the user program 121 directs, to the shared memory data collection means 1222, devices DO to D49 which represent number-of-finished-products data and are desired to be collected from the PLC 4b; a PLC-4b device data storage area 1221b on the shared memory location 1221 where the device data collected from the PLC 4b are to be temporarily stored; and a user buffer into which the device data are to be stored. The shared memory data collection means 1222 is then invoked.

In step S105, the shared memory data collection means 1222 directs, to protocol B device data collection means 1223b, device data desired to be collected from the PLC 4b; and the PLC 4b device data storage area 1221b on the shared memory location. The protocol B device data collection means 1223b is then activated.

In step S106, the user program 121 directs the shared memory data collection means 1222 to transport to the user buffer data pertaining to devices DO to D49, which represent product number data and are stored into the PLC 4b device data storage area 1221b in the shared memory location 1221 by the protocol-B device data collection means 1223b. Collection of, from the PLC 4b, the data pertaining to devices DO to D49 representing product number data is now completed.

In step S107, in order to collect, from the PLC 4c, data pertaining to devices R10 to 20 representing measurement data,the user program 121 directs, to the shared memory data collection means 1222, data pertaining to devices R10 to 20 representing measurement data desired to be collected from the PLC 4c; a PLC 4c device data storage region 1221c on the shared memory location 1221; and a user buffer where the collected device data are to be stored The shared memory data collection means 1222 is invoked.

In step S108, the shared memory data collection means 1222 directs, to protocol-C device data collection means 1223c, device data desired to be collected from the PLC 4c; and the PLC-4c device data storage area 1221c on the shared memory location. The protocol C device data collection means 1223c is then activated.

In step S109, the user program 121 directs the shared memory data collection means 1222 to transport to the user buffer data pertaining to devices R10 to 20, which are measurement data and are stored into the PLC 4c device data storage area 1221c of the shared memory location 1221 by the protocol C device data collection means 1223c. Collection of 26 data pertaining to devices R10 to 20, which are measurement data, from the PLC 4c is now completed.

Operations of the device data collection means 1223a, 1223b, and 1223c of the controller 100 will now be described by reference to FIGS. 4 and 5.

The device data collection means 1223a, 1223b, and 1223c di f f er f rom one another only in terms of protocols but perf orm identical processing procedures. Therefore, the operation of these device data collection means will be described by reference to the operation of the protocol-A device data collection means 1223a.

In order to collect, from the PLC 4a, data pertaining to devices WO to W99 representing product number data by means of the shared memory data collection means 1222, the protocolA device data collection means 1223a is activated upon receipt of an instruction for collecting data pertaining to devices WO to W99 representing product number data.

In step S201, the protocol-A device data collection means 1223a opens the communications line 5a in accordance with communication procedures of protocol A which are stored in the protocol-A device data collection means 1223a and assigned to the PLC 4a.

In step S202, the protocol-A device data collection means 1223a communicates with the PLC 4a and collects data 41a pertaining to devices WO to W99, which are product number data and are stored in the memory 40a of the PLC 4a.

In step S203, the protocol A device data collection means stores the thuscollected data pertaining to devices WO to W99, which are product number data, into the PLC-4a device data storage region 1221a on the predetermined memory location 1221 27 (see FIG. 5).

In step S204, the communications line Sa is closed in accordance with communication procedures with the PLC 4a.

Collection of data pertaining to devices WO to W99, which are product number data, from the PLC 4a is now completed.

In the first embodiment, the user designates a PLC from which data are tobe collected (i.e., an object fromwhichdevice data are collected), a user buffer for storing the thus- collected data, and a device data storage region on the shared memory location 1221. The data collection means stored in the memory is activated to automatically perform settings of-thecommunications protocol assigned to the PLC from which the data are collected and settings for opening or closing a line. After having been temporarily stored in the shared memory, the data collected from the PLC are stored in the user buffer designated by the user- Accordingly, it is essential requirement for the user to ascertain only the contents of the shared memory, and the user himself does not need to prepare a user program corresponding to each communications protocol every time data are processed. A program can be readily prepared without a necessity for expert knowledge of communications protocols, thus resulting in improved workability.

Since the collected data are temporarily stored in the shared memory, the only requirement of the user is that he take into consideration exchange of data between the shared memory and the user buffer even when the data are stored into the user buffer designatedby the user, thus rendering simple the program processed by the shared memory data collection means. Further, the time required for processing the program can be shortened, thus resulting in an improvement in the performance of the data 28 processor (i.e., the controller).

Further, in practice the device data collection means establishes communication with the PLC 4, and the user program makes access only to the shared memory, whereby processing capability of the data processor is also improved. Second Embodiment A data setting method according to a second embodiment of the present invention will now be described by reference to FIGS. 6 through 10.

FIG. 6 is a block diagram showing the configuration of a data setting device according to the present invention. - Inthe drawing, reference numeral 123 designates data setting means which operates within the memory 120. The reference numerals that are the same as those used in connection with the first embodiment designate identical or corresponding elements.

FIG. 7 is a functional diagram showing the function of the data setting means 123. In the drawing, reference numeral 1231 designates shared memory where device data to be set on the PLCs 4a, 4b, and 4c are stored; 12 32 designates shared memory data setting means which serves as data exchange means for exchanging device data between the shared memory 1231 and a designated user buffer; 1233 designates device data setting means which serves as device data processing means and is equipped with communications protocol storage means for storing a communications protocol assigned to the PLCs 4; 1233a designates device data setting means for use with the PLC 4a connected to the controller by means of protocol A; e.g., RS-232-C protocol; 1233b designates device data setting means for use with the PLC 4b connected to the controller by means 29 of protocol B; e.g., Ethernet protocol; and 1233c designates device data setting means for use with the PLC 4c connected to the controller by means of protocol C; e.g., original LAN protocol.

FIG. 8 is a flowchart showing the operation of the shared memory data setting means 1232. The flowchart shows the operation of the user program 121 and the operation of the shared memory data setting means 1232. In this flowchart, the user program 121 invokes the shared memory data setting means 1232, to thereby set data on the respective PLCs 4a, 4b, and 4c connected to the controller by way of dif f erent communicati-ons lines in the following sequence; that is, devices WO to W99 representing product number data relating to the PLC 4a; devices DO to D49 representing number-of-finished-products data relating to the PLC 4b; and devices R10 to 20 representing measurement data relating to the PLC 4c.

FIG. 9 is a flowchart showing the operation of the device data setting means 1233 when the device data setting means 1233 sets data on the PLCs 4. Particularly, the flowchart shows the operation of the protocol-A device data setting means 1233a when the protocol-A device data setting means 1233a sets, on the PLC 4a, data relating to devices WO to W99 representing product number data.

FIG. 10 is a diagram showing the contents of the shared memory location.

The operation of the data setting device according to the second embodiment will now be described.

First, the outline of operation of the data setting device will be described by reference to FIG. 7.

A user (operator) designates a device on which device data 3'0 are to be set; i.e., a PLC 4 on which device data are to be set, and a user buffer which stores device data to be set on the PLC 4.

The user program 121 written by the user invokes the shared memory data setting means 1232, and the thus-invoked shared memory data setting means 1232 stores, into the shared memory location 1221, the device data to be set on the PLC 4 and activates the device data setting means 1233a, 1233b, and 1233c. The thus-activated device data setting means 1233a, 1233b, and.1233c establish actual communication with the PLC 4a, PLC -4b, and PLC 4c in accordance with corresponding communications protocols stored in the respective device data setting means and set the device data on the respective PLCs 4a, 4b, and 4c.

In this way, the user can set device data on a specific PLC by designating a PLC on which device data are to be set and a user buffer which stores the device data used for setting.

By reference to FIGS. 8 and 10, there will be described in detail operations of the data processor or operations of the data processor for setting data; that is, setting of, the PLC 4a, data pertaining to devices WO to W99 representing product number data; setting of, on the PLC 4b, data pertaining to devices DO to D49 representing number-of-finishedproducts data; and setting of, on the PLC 4c, data pertaining to devices R10 to 20 representing measurement data.

The user prepares a user program for designating a PLC on which device data are to be set, a user buffer where the device 1 data to be set are stored, and a device data storage area on the shared memory location 1231. The thus-prepared user program is stored into the memory 120, and the processing to be performed by the user is now completed.

In the present embodiment, the above-described operations required to be performed by the user correspond to operations for setting the device data stored in the user buffer on the PLC 4a as devices WO to W99, which are product number data, setting the device data stored in the user buffer into the PLC 4b as devices DO to D49, which are number-off inishedproducts data, and setting the device data stored in the user buffer into the PLC 4c as devices R10 to 20, which are measurement data.

There will now be described the operation of the data setting means which are provided within the data setting device and operate according to the user program written by the user.

In step S301, the user program written by the user directs, to the shared memory data setting means 1232, devices WO to W99 representing product number data to be set on the PLC 4a; a PLC-4a device data storage area 1231a on the shared memory location 1231; and the user buffer in which the setting data are stored. The shared memory data setting means 1232 is invoked, and processing then proceeds to step S302.

In step S302, the shared memory data setting means 1232 stores the setting data acquired from the user program into the PLC-4a device data setting area 1231a on the shared memory location 1231, and processing then proceeds to step S303.

In step S303, a device desired to be set on the PLC 4a and the PLC-4a device data setting area 1231a on the share memory location 1231, where the device data collected from the PLC 4a 32 are to be stored, are directed to the protocol-A device data setting means 1233a - Then, the protocol-A device data setting means 1233a is activated, and the data pertaining to devices WO to W99, which represent product number data and are stored in the PLC-4a device data storage area 1231a on the shared memory location 1231, are set on the PLC 4a (activation of the PLC-4a device data storage area 1231a will be described later).

Processing then proceeds to step S304.

This completes a round of operations required for setting the data pertaining to devices WO to W99 representing product number data to the PLC 4a.

In step S304, in order to set, on the PLC 4b, the data pertaining to devices DO to D49 representing number-of- finished-products data, the user program 121 directs, to the shared memory data setting means 1232, devices DO to D49 which are number-of- finished-products data and are desired to be set on the PLC 4b; the PLC- 4b device data storage area 1231b formed on the shared memory location 1231; and a user buffer into which the setting data are to be stored. The shared memory data setting means 1232 is invoked. - In step S305, the shared memory data setting means 1232 stores, into the PLC-4b device data setting region 1231b formed on the shared memory location 1231, the setting data acquired from the user program.

In step S306, a device desired to be set on the PLC 4b and the PLC-4b device data setting region 1231b formed on the shared memory location 1231 are directed to the protocol-B device data setting means 1233b. The protocol-B device data setting means 1233b is activated so as to set, on the PLC 4b, devices DO to D49 stored in the PLC-4b device data storage area 33 1221b; that is, product number data. This completes setting of, on the PLC 4b, data pertaining to devices DO to D49 representing product number data.

In step S307, in order to set, on the PLC 4c, data pertaining to devices R10 to 20 representing measurement data, the user program 121 directs, to the shared memory data setting means 1232, devices R10 to 20, which are measurement data and are desired to be set on the PLC 4c; a PLC-4c device data setting region 1231c formed on the shared memory location 1231; and a user buffer where the device data are to be stored according to the user program 121. The shared memory data setting means1232 is invoked.

In step S308, the shared memory data setting means 1232 stores, into the PLC-4c device data setting region 1231c formed on the shared memory location 1231, the setting data acquired from the user program.

In step S309, a device desired to be set on the PLC 4c and the PLC-4c device data setting region 1231c formed on the shared memory location are directed to protocol-C device data setting means 1233c, and the protocolC device data setting means 1233c is activated. Devices R10 to R20 stored in the PLC-4c device data setting region 1231c; i. e., measurement data, are set on the PLC 4c. This completes setting of, on the PLC 4c, data pertaining to devices RIO to R20 representing measurement data.

Operations of the device data setting means 1233a, 1233b, and 1233c of the controller 100 will now be described by reference to FIGS. 9 and 10.

The device data setting means 1233a, 1233b, and 1233c perform identical processing procedures and differ from one 3i another only in terms of protocol. Therefore, the operation of these device data setting means will be described by reference to the operation of the protocol-A device data setting means 1233a.

In order to set, on the PLC 4a, devices WO to W99 representing product number data, an instruction for setting data pertaining to devices WO to W99 representing product number data is received f rom the shared memory data setting means 1232, whereby the protocol-A device data setting means 1233a is activated.

In step S401, the protocol-A device data setting me-ans 1233a opens the communications line 5a in accordance with communication procedures of protocol A, which are stored in the protocol-A device data setting means 1233a and assigned to the PLC 4a.

In step S402, data pertaining to devices WO to W99representing product number data used for setti ng are acquired from the PLC-4a device data setting region 1231a. In step S403, the protocol-A device data setting means communicates with

the PLC 4a and sets, in the memory 40a of the PLC 4a, the data 41a pertaining to devices WO to W99 representing product number data.

In step S404, the communications line 5a is closed in accordance with communication procedures with the PLC 4a. This completes setting of, on the PLC 4a, data pertaining to devices WO to W99 representing product number data.

In the second embodiment, the user designates a PLC where data are to be set (i.e., an object into which device data are to be set), a user buffer where the data used for setting are stored, and a shared memory location. As a result, the data setting means stored in the memory is activated to automatically perform settings of the communications protocol assigned to the PLC on which the data are to be set, as well as settings for opening or closing aline. After having been temporarily stored in the shared memory, the data used f or setting, which are stored in the user buffer, are stored in a designated memory of the PLC. Accordingly, the user himself does not need to prepare a user program corresponding to each communications protocol, every time data are processed. A program can be readily prepared without a necessity for expert knowledge of communications protocols, thus resulting in improved workability.

Since the data used for setting are temporarily stored in the shared memory, the only requirement of the user is that he take into consideration exchange of.data between the shared memory and the user buffer even wh.en the data are set on the PLC designated by the user, thus rendering simple the program processed by the shared memory data setting means. Further, the time required for processing the program can be shortened, thus resulting in an improvement in the performance of the data processor (i.e., the controller).

Third Embodiment A third embodiment of the present invention relating to a refresh-type data collection method will now be described by reference to FIGS. 11 through 14.

FIG. 11 is a block diagram showing the configuration of a refresh-type data collection device according to the present invention.

In the drawing, reference numeral 124 designates refresh-type 36 data collection means which operates within memory 120. Those reference numerals which are the same as those used in connection with the first and second embodiments designate identical or corresponding elements.

FIG. 12 is a functional diagram showing the function of the refresh-type data collection means 124 which operates within the memory 120. In the drawing, reference numeral 1241 designates shared memory which is provided within the memory 121 and in which the device data retained by the PLCs 4a, 4b, and 4c are stored; 1242 designates data collection means which serves as data exchange means for exchanging device data between. the shared memory provided in the memory 120 and a designated user buffer; 1243 designates device data collection refresh means which serves as device data processing means and is equipped with communications protocol storage means for storing a communications protocol assigned to the PLCs 4; 1243a designates device data collection refresh means for use with the PLC 4a connected to the controller by means of protocol A; e.g., RS-232-C protocol; 1243b designates device data collection refresh means for use with the PLC 4b connected to the controller by means of protocol B; e.g., Ethernet protocol; and 1243c designates device data collection refresh means for use with the PLC 4c connected to the controller by means of protocol C; e.g.-, original LAN protocol.

FIG. 13 is a flowchart showing the operation of the shared memory data collection means 1242. The flowchart shows the operation of the user program 121 and the operation of the shared memory data collection means 1242. In this flowchart, the user program 121 invokes the shared memory data collection means 1242, to thereby collect data in the following sequence from the 37 respective PLCs 4a, 4b, and 4c, which are connected to the controller by way of different communications lines, while performing refresh operation; devices WO to W99 representing the product number relating to the PLC 4a; devices DO to D49 representing number-of-finished-products data relating to the PLC 4b; and devices R10 to 20 representing measurement data relating to the PLC 4c.

FIG. 14 is a flowchart showing the operation of the device data collection refreshing means 1243 when the device data collection refreshing means 1243 collects data from the PLCs 4. Particularly, the flowchart shows the operation of the protocol-A device data collection refreshing means 1243a when the protocol-A device data collection refreshing means 1243a collects, from the PLC 4a, data relating to devices WO to W99 representing product number data.

The operation of the data collection device according to the third embodiment will now be described. First, the outline of operation of the data collection device will be described by reference to FIG. 12.

A user designates device data which the user desires to collect; i. e, a PLC where the device data are stored; a user buffer where the thuscollected device data are to be stored; a device data storage area on the device shared memory location 1241; and storage timing used for performing data refresh operation.

In response to the PLC being designated by the user, the CPU 110 directs the PLC designated by the user to the device data collection refreshing means 1243a, 1243b, and 1243c, and activates the device data collection refreshing means 1243a, 1243b, and 1243c.

38 In accordance with communications protocols stored in the respective device data collection refreshing means 1243a, 1243b, and 1243c, the device data collection refreshing means 1243a, 1243b, and 1243c establish actual communication with the PLC 4a, PLC 4b, and PLC 4c in synchronization with the storage timing, thereby collecting device data from the PLC 4a, PLC 4b, and PLC 4c and storing the thus-collected device data into the device data storage area on the shared memory location 1241.

The shared memory data collection means 1242 stores, ino the user buf f er designated by the user, the device data rel.ating to the PLC 4a, PLC 4b, and PLC 4c, which are collected by _thedevice data collection refreshing means 1243a, 1243b, and 1243c: in synchronization with storage timing and are stored in the shared memory location 1221.

In this way, the -user can collect device data from a designated PLC while performing refresh operation, by designation of only a PLC from which the user desires to collect device data, a user buffer into which the thus-collected device data are to be stored, the device data storage area, and the storage timing for data refresh operation.

By reference to FIGS. 5 and 13, there will be described in detail operations of the data processor or operations of the data processor for collecting data; that is, data pertaining to devices WO to W99, which represent the product number, from the PLC 4a; data pertaining to devices DO to D49, which represent number-of-finished-products data, from the PLC 4b; and data pertaining to devices R10 to 20, which represent measurement data, from the PLC 4c.

First, an explanation will be given of an operation required when the user himself writes a user program into 39 memory.

The user prepares a user program for designating a PLC where device data desired to be collected are stored, a user buf f er where the collected device data are to be stored, a device data storage area, and storage timing used for data refresh operation. The thus-prepared user program is stored into the memory 120, thus completing the processing to be performed by the user.

In the present embodiment, the above-described operations required to be performed by the user correspond to an operation for collecting, from the PLC 4a, data pertaining to devices WO to W99 representing product number data; an operation for storing the thus-collected device data into the user buffer; an operation for collecting, from the PLC 4b, data pertaining to devices DO to D49 representing number-of-finished-products data; an operation for storing the thus-collected device data. into the user buf f er; an operation f or collecting, f rom the PLC 4c, data pertaining to devices R10 to 20 representing measurement data; and an operation for storing the thuscollected device data into an arbitrary user buffer. Thus, the user designates, three times in sequence, a PLC where desired device data are stored and a user buffer where the collected device data are to be stored.

There will now be described the operation of the data collection refreshing means which are provided within the data collection device and operate according to the user program written by the user.

In step S501, according to the user program written by the user, devices WO to W99, which are product number data to be collected from the PLC 4a; a PLC-4a device data storage area 1221a on a shared memory location 1241 where the device data collected from the PLC 4a are to be temporarily stored; the user buffer into which the device data are to be finally stored; and storage timing, are directed to the shared memory data collection means 1242. The shared memory data collection means 1242 is invoked, and processing then proceeds to step S502.

In step S502, the shared memory data collection means 1242 selects a communications protocol used when communication is actually established with the PLC 4a; that is, protocol-A device data collection refreshing means 1243a, from the communicat-ion' protocols which are stored in advance so as to correspond to the respective PLCs connected to the controller 100. The device data desired to be collected from the PLC 4a, the PLC-4a device data storage area 1221a on the shared memory where the device data collected from the PLC 4a temporarily are to be stored, and storage timing, are directed to the protocol-A device data collection refreshing means 124 3a. The protocol-A device data collection refreshing means 1243a is activated, to thereby temporarily store the device data stored in the PLC 4a; that is, the product number data, into the shared memory location 1241 (the operation of the protocol-A device data collection refreshing means 1243a will be described later). Processing then proceeds to step S503.

In step S503, in accordance with the user program. the data pertaining to devices WO to W99, which represent product number data and are stored by means of the protocol-A device data collection refreshing means 1243a, are transported from the PLC-4a device data storage area 1241a in the shared memory location 1241 to the user buffer specified by the user.

-11 A round of operations required for storing the data pertaining to devices WO to W99, which are the product number data collected from the PLC 4a, into the user buffer designated by the user are now completed through the processing relating to steps S501 to S503.

In order to collect, from the PLC 4b, the data pertaining to devices DO to D49 representing number-of-finished-products data, the user program 121 directs, to the shared memory data collection means 1242, devices DO to D49 which represent number-of-fi nished-products data and are desired to be collected from the PLC 4b; a PLC-4b device data storage area1241b on the shared memory location 1241 where the device data collected from the PLC 4b are to be temporarily stored; the user buffer into which the device data are to be stored; and storage timing. The shared memory data collection means 1242 is then invoked.

In step S505, the shared memory data collection means 1242 directs, to protocol-B device data collection refreshing means 1243b, a device data storage area 1221b which stores device data desired to be collected from the PLC 4b; the PLC-4b device data storage area 1241b on the shared memory location; and storage timing. The protocol-B device data collection refreshing means 1243b is activated.

In step S506, through use of the shared memory data collection means 1242, the user program 121 collects the data pertaining to devices DO to D49 representing product number data stored by the protocol-B device data collection refreshing means 1243b, from the PLC-4b device data storage area 1241b in the shared memory location 1241. The thus-collected data are stored in the user buffer.

42 This completes collection of, from the PLC 4b, the data pertaining to devices DO to D49 representing product number data.

In step S507, in order to collect, from the PLC 4c, data pertaining to devices RIO to 20 representing measurement data, the user program 121 directs, to the shared memory data collection means 1242, devices R10 to 20 representing measurement data desired to be collected from the PLC 4c; a PLC-4c device data storage region 1241c on the shared memory location 1241; a user buffer where the collected device data are to be stored; and storage timing. The shared memory data collection means 1242 is invoked.

In step S508, the shared memory data collection means 1242 directs, to protocol-C device data collection means 1243c, a device data storage area 1221c which stores device data desired to be collected from the PLC 4c; a PLC-4c device data storage area 1241c on the shared memory location; and storage timing. The protocol-C device data collection refreshing means 1243c is activated.

In step S509, through use of the shared memory data collection means 1242, the user program 121 collects the data pertaining to devices R10 to R20 representing measur.ement data stored by the protocol-C device data collection refreshing means 1243c, from the PLC-4c device data storage area 1241c on the shared memory location 1241. The thus-collected data are stored in the user buffer. This completes collection of, from the PLC 4c, the data pertaining to devices R10 to R20 representing measurement number data.

In step S510, a selection is again made as to whether 43 device data are collected from the PLCs 4a, 4b, and 4c. If collection of device data is continuously performed, device data relating to the PLC 4a are collected from the shared memory location 1241 in step S511.

Similarly, device data relating to the PLC 4b are collected in step S512, and device data relating to the PLC 4c are collected in step S513.

If processing is terminated in step S514, the data collection refreshing means of the individual devices are deactivated in steps S515, S516, and S517.

In contrast, if processing is not terminated, processing then returns to step S511, where collection of device data is resumed- operations of the device data collection refreshing means 1243 will now be described by reference to FIGS. 5 and 14.

The device data collection refreshing means 1243a, 1243b, and 1243c perform identical processing procedures and differ from one another only in terms of protocols. Therefore, the operation of these device data collection refreshing means will be described by reference to the operation of the protocolA device data collection refreshing means 1243a.

In order to collect, from the PLC 4 a by means of the shared memory data collection means 1242, data pertaining to devices WO to W99 representing product number data, the protocol-A device data collection refreshing means 1243a is activated, upon receipt of an instruction for collecting data pertaining to devices WO to W99 representing product number data.

In step S601, the communications line 5a is opened in accordance with communication procedures of protocol A which are stored in the protocol-A device data collection means 1243a -111 and assigned to the PLC 4a.

In step S602, the protocol-A device data collection refreshing means 1243a communicates with the PLC 4 a and collects data 41a pertaining to devices WO to W99, which represent product number data and are stored in the memory 40a of the PLC 4a.

In step S603, the thus-collected data pertaining to devices WO to W99 representing product number data are stored into the PLC-4a device data storage region 1241a on the predetermined memory location 1241 (see FIG. 5).

In step S604, processing is suspended until the stor.agetiming specified by the user.

In step S605, if the user program 121 issues a t.ermination request by way of the shared memory data collection means 1242, the communications line 5a is closed in accordance with the communications procedures assigned to the PLC 4a in step S606. If no termination request is issued, processing is repeatedly performed from step S602. This completes continuous collection of, from the PLC 4a, data pertaining to devices WO to W99 representing product number data.

In addition to the advantageous result yielded in the first embodiment, the third embodiment also yields an advantage of the ability to collect the latest device data at all times by reading the shared memory locations 1241a, 1242b, and 1241c which are refreshed at the timing designated by the user, without involvement of access to the PLC connected to the data processor by means of different protocols every time.

Further, the overhead communications time is reduced, thereby improving the performance of the data processor.

Fourth Embodiiment A refresh-type data setting method according to a fourth embodiment of the present invention will now be described by reference to FIGS. 15 through 18.

FIG. 15 is a block diagram showing the configuration of a refresh-type data setting device according to the present invention. In the drawing, reference numeral 125 designates refresh-type data setting means which operates within the memory 120. Those reference numerals that are the same as those used in connection with the first embodiment designate identical or corresponding elements.

FIG. 16 is a functional diagram showing the function of the refresh-type data setting means 125 which operates within the memory 120 shown in FIG. 15. In the drawing, reference numeral 1251 designates a shared memory location where device data retained by the PLCs 4a, 4b, and 4c are stored; 1252 designates shared memory data setting means which serves as data exchange means for exchanging device data between the shared memory location 1251 and a designated user buffer; 1253 designates device data setting refreshing means which serves as device data processing means and is equipped with communications protocol storage means for storing communications protocols assigned to the respective PLCs 4; 1253a designates device data setting refreshing means for use with the PLC 4a connected to the controller by means of protocol A; e.g., RS-232-C protocol; 1253b designates device data setting refreshing means for use with the PLC 4b connected to the controller by means of protocol B; e.g., Ethernet protocol; and 1253c designates device data setting refreshing means for 16 use with the PLC 4c connected to the controller by means of protocol C; e. g., original LAN protocol.

FIG. 17 is a flowchart showing the operation of the shared memory data setting means 1232. The flowchart shows the operation of the user program 121 and the operation of the shared memory data setting means 1232. As shown in this flowchart, the user program 121 invokes the shared memory data setting means 1252, to thereby set data on the respective PLCs 4a, 4b, and 4c connected to the controller by way of different communications lines in the following sequence; that is, devices WO to W99 representing product number data relating- to the PLC 4a; devices DO to D49 representing number-of- finished-products data relating to the PLC 4b; and devices R10 to 20 representing measurement data relating to the PLC 4c.

FIG. 18 is a flowchart showing the operation of the device data setting means 1253 when the device data setting means 1253 sets data on the PLCs 4. Particularly, the flowchart shows the operation of the protocol-A device data setting means 12 53a when the protocol-A device data setting means 1253a sets, on the PLC 4a, data relating to devices WO to W99 representing product number data.

The operation of the data setting device according to the fourth embodiment will now be described.

First, the outline of operation of the data setting device will be described by reference to FIG. 16.

A user designates device data where device data are to be set; i.e., a PLC 4 which is an object of setting; a user buffer where device data to be set on the PLC 4 are set; a device data setting area on the device shared memory location 1251; and storage timing used for performing refresh operation at the time 4 7 of setting of device data.

The shared memory data setting means 1252 invoked by the user program 121 stores the device data to be set on the PLC 4 into the shared memory location 1251, to thereby activate the device data setting refreshing means 1253a, 1253b, and 1253c. The thus-activated device data setting refreshing means 1253a, 1253b, and 1253c acquire device data from the shared memory location 1251 in agreement with storage timing. Further, in accordance with corresponding communications protocols stored in the respective device data setting refreshing means, the device data setting refreshing means 1253a, 1253b, and 1253cestablish actual communication with the PLC 4a, PLC 4b, and PLC 4c and set the device data on the respective PLCs 4a, 4b, and 4c.

In this way, the user can set device data on a specified PLC while refresh operation is performed by designating a PLC on which device data are to be set, a user buf f er where the device data used for setting are stored, a device data setting region, and storage timing.

By reference to FIGS. 15 and 17, there will be described in detail operations of the data processor or operations of the data processor; that is, setting of, on the PLC 4a, data pertaining to devices WO to W99 representing product number data; setting of, on the PLC 4b, data pertaining to devices DO to D49 representing number-of-finished-products data; and setting of, on the PLC 4c, data pertaining to devices R10 to 20 representing measurement data.

There will now be described the operation of the data setting refreshing means which are provided within the data processor and operate according to the user program written by 48 the user.

In step S701, the user program written by the user directs, to the shared memory data setting means 1252, devices WO to W99 representing product number data desired to be set on the PLC 4a; a PLC-4a device data storage area 1251a on the shared memory location 1251 where the device data are to be temporarily stored; a user buffer in which the setting data are stored; and storage timing. The shared memory data setting means 1252 is invoked, and processing then proceeds to step S702.

In step S702, in accordance with the user program, the shared memory data setting means 1252 transports the device data. desired to be set on the PLC 4a from the user buffer to the user program into the PLC-4a device data setting area 1251a on the shared memory location 1251, and processing then proceeds to step S703.

In step S703, t he shared memory data setting means 1252 directs, to the protocol-A device data setting refreshing means 1253a, a device desired be set on the PLC 4a, and the PLC-4a device data setting area 1251a on the share memory location 1251.

Then, the protocol-A device data setting means 1253a is activated, and the data pertaining to devices WO to W99, which represent product number data and are stored in the PLC-4a device data storage area 1251a on the shared memory location 1251, are set on the PLC 4a (activation of the PLC-4a device data storage area 1251a will be described later) Processing then proceeds to step S704.

This completes a round of operations required for setting to the PLC 4a the data pertaining to devices WO to W99 representing product number data.

In step S704, in order to set, on the PLC 4b, data 19 pertaining to devices DO to D49 representing number-offinished-products data, the use program 121 directs, to the shared memory data setting means 1252, devices DO to D49 which represent number-of-finished-products data and are desired to be set on the PLC 4b; a PLC-4b device data storage area 1251b formed on the shared memory location 1251; a user buffer into which the setting data are to be stored; and storage timing. The shared memory data setting means 1252 is invoked.

In step S705, the shared memory data setting means 1252 stores, into the PLC-4b device data setting region 1251b formed on the shared memory location 1251, the setting data acquired from the user program.

In step S706, a device desired to be set on the PLC 4b and the PLC-4b device data setting region 1251b formed on the shared memory location 1251 are directed to the protocol-B device data setting refreshing means 1253b. The protocol-B device data setting refreshing means 1253b is activated so as to set, on the PLC 4b, devices DO to D49 stored in the PLC4b device data storage area 1221b; that is, product number data. This completes setting of, on the PLC 4b, data pertaining to devices DO to D49 representing product number data.

In step S707, in order to set, on the PLC 4c, data pertaining to devices R10 to 20 representing measurement data, the user program 121 directs, to the shared memory data setting means 1252, devices R10 to 20, which represent measurement data and are desired to be set on the PLC 4c; a PLC4c device data setting region 1251c formed on the shared memory location 1251; a user buf fer where the device data are to be stored; and storage timing. The shared memory data setting means 1252 is invoked.

In step S708, the shared memory data setting means 1252 stores, into the PLC-4c device data setting region 1251c formed on the shared memory location 1251, the setting data acquired from the user program.

In step S709, a device desired to be set on the PLC 4c and a PLC-4c device data setting region 1251c formed on the shared memory location 1251 are directed to protocol-C device data setting means 1253c, and the protocol-C device data setting means 1253c is activated. Devices R10 to R20 stored in the PLC-4c device data setting region 1231c; i. e., measurement data, are set on the PLC 4c.

This completes setting of, on the PLC 4c, data pertaininq to devices R10 to R20, representing measurement data.

In step S710, a selection is again made as to whether device data are to be set on the PLCs 4a, 4b, and 4c. If device data are continuously set on the PLCs 4, device data relating to the PLC 4a are transported from the shared memory location 1251 at preset timing in step S711 while refresh operation is performed.

Similarly, device data are set oh the PLC 4b in step S712, and device data are set on the PLC 4c in step S713.

If processing is terminated in step S714, the individual device data setting refreshing means are deactivated in steps S716, S717, and S718.

* In contrast, if processing is not terminated, processing returns to step S711, where setting of device data is resumed.

Operations of the device data setting refreshing means 1253a, 1253b, and 1253c of the controller 1 will now be described by reference to FIGS. 16 and 18.

The device data setting refreshing means 1253a, 1253b, and 1253c perform identical processing operations and differ 51 from one another only in terms of protocol. Therefore, the operation of these device data setting refreshing means will be described by reference to the operation of the protocolA device data setting refreshing means 1253a.

In order to set, on the PLC 4a, devices WO to W99 representing product number data, an instruction for setting data pertaining to devices WO to W99 representing product number data is received f rom the shared memory data setting means 1252, whereby the protocol-A device data setting refreshing means 1233a is activated.

In step S801, the protocol-A device data setting me-ans1253a opens the communications line 5a in accordance with communication procedures of protocol A, which are stored in the protocol-A device data setting means 1253a and are assigned to the PLC 4a. In step S802, data pertaining to devices WO to W99 representing product

number data used for setting are acquired from the PLC-4a device data setting region 1251a. In step S803, the protocol-A device data setting means communicates with the PLC 4a and sets, in the memory 40a of the PLC 4a, the data 41a pertaining to devices WO to W99 representing product number data.

In step S804, the data processor awaits until storage timing designated by the user.

In step S805, if the user program 121 issues a termination request by way of the shared memory data collection means 1252, processing proceeds to step S806, where the communications line 5a is closed in accordance with the communications procedures. If no termination request is issued, refresh setting is repeatedly performed from step S802.

52 This completes continuous setting of, on the PLC 4a, data pertaining to devices WO to W99 representing product number data.

In the fourth embodiment, the user designates a PLC where data are to be set, a user buf f er where the data used for setting are stored, a shared memory location, and storage timing. As a result, the data setting means stored in the memory is activated to automatically perform settings of the communications protocol assigned to the PLC on which the data are to be set, as well as settings for opening or closing a line. After having been temporarily stored in the shared memory, -the data used for setting, which are stored in the user buffer, are stored in a designated memory of the PLC. Accordingly, the user himself is not required to prepare a u-ser. program corresponding to each communications protocol, every time data are processed. A program can be readily prepared without necessity for expert knowledge of communications protocols, thus resulting in improved workability.

Further, since the device data used for setting are temporarily stored in the shared memory, the processing to be performed by the program of the shared memory data setting means at the time of setting the data on the PLC designated by the user becomes simple in configuration, thus shortening the time required by the program to perform processing and resulting in improved performance of the programmable controller.

The latest device data can be set at all times by means of reading the shared memory locations 1251a, 1252b, and 1251c which are refreshed at the timing designated by the user, without involvement of access to the PLC connected to the data processor by means of different protocols every time.

53 Further, the overhead communications time is reduced, thereby improving the performance of the data processor.

Fifth Em1bodi-ment A fifth embodiment of the present invention, relating to a data collection method, will now be described by reference to FIGS. 19 through 22.

FIG. 19 is a block diagram showing the configuration of a data collection device according to the present invention. Reference numeral 6 designates an auxiliary storage device for storing a setting data file 61 (see FIG. 22); 126 designatesdata collection means which operates within the memory 120; and 151 designates an auxiliary storage device interface with the auxiliary storage device 6. Those reference numerals which are the same as those used in the previous embodiments are assigned to identical or corresponding elements.

FIG. 20 is a functional diagram showing the function of the data collection means 126, which operates within the memory 120. In the drawing, reference numeral 1261 designates a shared memory location where device data retained by the PLCs 4a, 4b, and 4c are stored; 1262 designates shared memory data collection means which serves as data exchange means for exchanging device data between the shared memory location 1261 provide d in the memory 120 and a designated user buffer; 1263 designates device data collection means which serves as device data processing means and is equipped with communications protocol storage means for storing respective communications protocol assigned to the PLCs 4; 1263a designates device data collection means for use with the PLC 4a connected to the controller by means of protocol A; e.g., RS-232-C protocol; 1263b designates device 541 data collection means for use with the PLC 4b connected to the controller by means of protocol B; e.g., Ethernet protocol; and 1263c designates device data collection means for use with the PLC 4c connected to the controller bymeans of protocol C; e.g., original LAN protocol.

FIG. 21 is a flowchart showing the operations of the protocol-A device data collection means 1263a, those of the protocol-B device data collection means 1263b, and those of the protocol-C device data collection means 1263c.

FIG. 22 is a table showing a database-type file (hereinafter referred to as a "setting data file") stored inthe auxiliary storage device'6 for reserving data pertaining to intervals at which device data are collected from a PLC. The operation of the data collection device according to the fifth embodiment will now be described. First, the outline of operation of the data collection device will be described by reference to FIGS. 19 and 20.

A user enters the "name of PLC device data collection protocol" and "intervals at which device data are collected from a PLC" by way of the keyboard 3. The thus-entered data are reserved in a setting data file 61 stored in the auxiliary storage device 6 (see FIG. 22). Next, the protocol-A device data collection means 1263a, the protocol-B device data collection means 1263b, and the protocol-C device data collection means 1263c refer to the setting data file 61 stored in the auxiliary storage device 6. The PLC device data retained by the PLCs 4 are stored in the shared memory 1261.

In this way, the user can set the device data collection timing as setting data in the auxiliary storage device in database format, without involvement of a setting operation by the user program. Through use of the setting data file, the device data collection means for various protocols can store the PLC device data into the shared memory at preset time intervals.

operations of the protocol-A device data collection means 1263a, those of the protocol-B device data collection means 1263b, and those of the protocol-C device data collection means 1263c, all being provided in the controller 1, will now be described by reference to FIGS. 19 through 22.

As shown in the flowchart shown in FIG. 21, the shared memory data collection means 1262 invokes the protocol-A devicedata collection means 1263a, the protocol-B device data collection means 1263b, and the protocol-C device data collection means 1263b, all of which are expanded on the memory 120. In step S901, a PLC device data collection interval is read by reference to the name of PLC device data collection protocol of the setting data file 61 stored in the auxiliary storage device 6. In step S902, the data processor awaits a time period corresponding to the PLC device data collection interval set by the user. Processing then proceeds to step S903, and PLC device data are transported from the PLCs 4 to the shared memory 1221 so as to correspond to the respective protocols. Processing then returns to step S902.

According to the fifth embodiment, the user is not required to describe intervals for collecting device data from PLCs as a user program. Collection intervals are set as a parameter for each collection protocol. Even if there is a change in the collection intervals, there is no need to modify the entire user program, and the only requirement of the user 56 is that he change the portion of the program set as a parameter, thereby enabling easy modification of the settings for device data collection and resulting in improved programming workability.

Sixth Embodiment A sixth embodiment of the present invention, relating to a data collection method will now be described by reference to FIGS. 23 to 29.

FIG. 23 is a diagram showing the system configuration of a data collection apparatus according to the present invention. In the drawing, reference numerals 100, 101, and 102 designate identical or corresponding controllers, which double as shared memory and refresh-type data collection means.

The controllers lob, 101, and 102 are connected together over a communications line 5e serving as a second communications line, by means of single protocol E; e.g., Ethernet protocol.

Through use of one protocol, the PLC 4a is connected to the controller 100 by means of the communications line 5a serving as the first communicatio ns line; through use of another protocol a PLC 4d is connected to a controller 101 by means of a communications line 5d serving as the first communications line; and through use of still another protocol a PLC 4f is connected to a controller 102 by way of a communication line 4f serving as the first communications line.

FIG. 24 is a functional diagram showing the functions of the data collection means that operate within the memory. In the drawing, reference numeral 121 designates a user program which accesses shared memory 1271 by means of unified communications procedures; 127 designates refresh-type data 57 collection means which operates within the memory 120; and 142 designates an interface for protocol E for connecting controllers 101 and 102 by way of the communications line 5e and by means of a single communications protocol.

In the refresh type data collection means 127, reference numeral 1271 designates shared memory which stores device data retained by the PLC4a; device data which are retained by the PLC 4d and transmitted from the controller 101 and received by the controller 100; and device data which are retained by the PLC 4e and transmitted from the controller 102 and received by the controller 100. Reference numeral 1272 designates sharedmemory data collection means which serves as data exchange means for exchanging device data between the shared memory location 1271 provided in the memory 120 and a designated user buffer; 1273a designates device data collection refreshing means serving as device data processing means equipped with communications protocol storage means for storing protocol of the PLC 4a connected to the controller by means of protocol A; e.g., RS-232-C protocol. Reference numeral 1274 designates write request transmission means for transmitting a request for writing the device data stored in the shared memory 127 of the controller 100 to either one of the controllers 101 and 102. Reference numeral 1275 designates write means which receives the write request transmitted from either one of the controllers 101 and 102 and writes the device data on the shared memory 1271 of the controller that has transmitted the request. Reference numeral 1276 designates means for activating the write request transmission means 1274 at established intervals.

Reference numeral 1271d designates a device refresh parameter storage area within the shared memory 1271. In the 5S shared memory 1271, there are stored a refresh range used for transmitting the device data from the shared memory 1271 of the controller 100 to either one of the controllers 101 and 102 and for storing the device data of either one of the controllers 101 and 102, whichever controller has transmitted the write request, in the device data area on the shared memory 1271. Further, the shared memory 1271 stores a device refresh parameter including time intervals used for transmitting device data from the shared memory 1271 of the controller 100 to either one of the controllers-101 and 102. Reference numeral 21 designates an interval at which device dataon the shared memory are refreshed in the controllers 100, 101, and 102; and 22 designates a range in which device data are transmitted from the controller 100 to either one of the controllers 101 and 102. For example, the range is set such that data pertaining to WO to W99 and DO to D99 are transmitted to the respective controllers 101 and 102. Similarly, reference numeral 23 designates a range in which device data are transported from the controller 101 to either one of the controllers 100 and 102. For example, the range is set such that data pertaining to devices W200 to W299 and data pertaining to devices D100 to D199 are transported to the respective controllers 100 and 102. Similarly, reference numeral 24 designates a range in which device data are transported from the controller 102 to either one of the controllers 100 and 101. For example, the range is set such that data pertaining to devices W200 to W299 and data pertaining to devices RO to R99 are transported to the respective controllers 100 and 101.

FIG. 26 is a schematic representation showing one example 59 of contents of device write request transmission data to be transmitted to another controller. As shown in the drawing, the device write request transmission data comprise the number of data sets, 25, assigned to a single controller of a refresh parameter; the type of device, 26, described in setting 1 of the refresh parameter; a header number of a device, 27, described in setting I of the refresh parameter; the number of transported bytes, 28, described in the setting 1 of the refresh parameter; and device data 29 described in the setting 1 of the refresh parameter.

FIG. 27 is a flowchart showing the operation of means-for" activating means of transmitting a request for writing device data from the controller to another controller at established intervals, in accordance with the refresh parameter.

FIG. 28 is a flowchart showing the operation of means for transmitting a request for writing device data from the controller to another controller at established intervals, in accordance with the refresh parameter.

FIG. 29 is a flowchart showing the operation of means which receives a write request transmitted from another controller and writes the thusreceived write request into the shared memory.

The operation of the data collection device according to the sixth embodiment will now be described. First, the outline of operation of the data collection device will be described by reference to FIG. 24.

The means 1276, which activates means for issuing a request for writing the device data stored in the controller to another controller at established intervals in accordance with the refresh parameter set by the user, reads a refresh fa (1) (1) Q) (a 4--) 1 "a 4) r- a) (a 4 r= 70 a 4 Q) 0) Q -f W 4--) U) " Q) J 'A r- 4-1 a) 0 a) (D 0 4 a) fli H (a (a a) qr > 4-) 4-J (a -W Q) 4 4 r-4 44 ra > 4 1-4 a 0 r-A r-l -0 >1 a) a) 44 fu 4-) 0 (1) W 0 ol a) -C (1) 4J f o J= w 41 70 r-4 4-) u a) a) Q) u 4-) -Q _4 a) m a) U) 0) r-f (a 0 4 70 4 U to -l r-A a) _0 3: rA > a) r-I aj 0 4J 4 4 a) ra -0 a) 0 4J w ru $-4 4-J w -0 0 > 4) 4-4 1 a) 0 > p a 0 W 4-1 4-1 4 Ef) 0 U) 4-4 (1) 44 4) 4 4-) 70 4-) r -4 a) r- a) -4 4 (1) -q a 41 C: C:

U) 4) 0 4 4-J (a -0 (-) 4-J w (n a) 0 0 0) Irr F 0 a) a) 1: r- 4-) -0 a) En Q) 4 r- ro ru J-- c 4 in 4-j 4) w 0 C:

a) CNJ 4 $-4 4-) 4-) a) 1-4 4 144 V) li -Q- 0 U) (n 0 a), 4-1 44 J-) 0 'A a) X- Li A 44 _0 0 70 a) (a 04 $4 41 U) 0 0 0 V) flu C: 5 > U) C) ro C: U) 0 >, D W 0 W ru 4 C 4) -4 -a U) 4 ru 4 0 (a Q) U $4 M 4J 41 4 _4 _j C M 0 ro ri 4-) >1 W IL 44 Ei j r-I Co r- a) C:

> 0 4 U) C:) 0 a) 4 -C 0 w 0 a) (a 4 -1 4J CL I: 'A 4-) 70 Ei E 44 (n 0 4 -0 -0 -0 L) 41 fu a) tn a) rA a) 70:3: 4 4 0 U) 0 a) 4 0 -r 4.j C v M as a) (- 3: fu 44 a) U) 0, W >1 r-j V) CD 44 tlo.14 0 0 w 4 r-I (1) W 0 lqr V) I-i o 0 -4 4 4 44 4 0 3 41 r- (a (o -0 0 4 En 0 a) m V) E a) 4-) 1-4 >1 (13 ru 4-1 -Q (1) 0 a) fu > a) 4 (o S_- 4 M a) L) 0 4J 41 " r- 4 S-4 (,j a) 4 0 4) U) 0 a) 44 4 41 0 p c 4 0 LD 0 > 4 4-J 0 0 o 0 4 a) C: v C 4J (U 4-) 0 E rz 0 C) r 0 M ru a) 4--) a) 4--) e 4J 0 W 0 r-4 -Q W p 4J a) > 4-) E (13 c a) (n 4 P C 4 4 4 w e 0 0 W ra "a W M 0 4J 44 a) S.4 d) 44 41 4--) 4-1 -H C: -4 $4 0 a) ri fu -0 W 0 r-4 -0 0 44 $4 0 1 V -0 C) U) v -0 V 4 r-A Lf) (1) 0 tP 0 4 4J 1-1 0. M 4) " 0 ru 0 0 0 r- 4 C: -4 (1) a) -0 W 4 0 a 41 0 ro 4 4 a) o ru 5-4 C) -r-I V) -4 W --f C) U) 4-3 44 4 ra - 0.0 C_ CD 4--) r- 1-4 C) 0 C: U) 0 4 r-I M.,1 0 U) " (a -4 44 to a) 0 0 U) (a a) U) P-- r= 4 -,I r-4 > U) 4 (n 4-1 4) 4 14 4-) cq 0 u C: E 44 0, H tf) 4j 4 70 C) a) 4 0 U 4-) w 0 1-- fu M a) V Fz: CD (a (1) a) m 4-) 4 a) 4 4) 4_j 0 14 14 4 -4 41 4--) r 4J (U _j 0 ra 0 " Q) v 4-J ro fa -r-I 4-1 4) C: rz ro U) tu 4 4 C: in r- 0 U) -0 F- (a V 0) a) a) 0 a) 0, 41 4 fa -i " m r- 4 (n -0 4 0 0 V 4 C:

0 c (N 0 5: 0 (U 41 4-) " c C: E (- 0 4-J 4-) > u 0 ra 4 r-f 0 U) 4) ol (n a) >1 x -0 a) L) 4 u U) 4 r- Q) (D E ru 0) 70 a) ro r-4 (a 4J '-I c Q) (a E m 4 ro:3 M 4 4 0 r- 44 a) ru v 0 (D 4J 44 4J (V IY 0 4 0 4-4 a) d) 4) 4 514 r- 0 4 c m a) a) V) 4) 4 (a 4--) a) 4 4 -1 70 V -r-i 4-) 44 4-) 4:3 W 4-4 L U) w E (o the controller 100, data pertaining to the number-of -data-sets 25, the type-of-device 26, the header-number-of -device 27, and the number-of - transport ed-bytes 28 are fetched and arranged in a format such as that shown in FIG. 26. From the data sets, a write request transmission data for another controller is prepared.

In step S1004, the write request transmission data for another controller is directed to the write request transmission means 1274, thereby activating the write request transmission means 1274.

In step S1005, the data collection device performs -itsown routine and awaits execution only for a time period corresponding to the device refresh interval 21 read from the refresh parameter, until the write request transmission means 1274 is activated.

There is a case where the refresh parameter 20 on the device refresh parameter storage area 127 ld on the shared memory may be modified by the user program 121. In this case, processing will again be performed from processing relating to step S1001.

On the basis of the foregoing flowchart, the write request transmission means 1274 for writing the device data of the controller to another controller is activated periodically, at the refresh intervals specified by the user.

The operation of the write request transmission means 1274, which is used for transmitting to another controller a request for transporting device data of the controller, will now be described by reference to a flowchart shown in FIG. 28.

In step S1101, the write request transmission data for another controller directed by the means 1276 are retrieved, G2 and the device data are read from the shared memory 12-71. The write request transmission data for another controller are set in the device data 29, thereby completing preparation of transmission data.

In step S1102, the refresh parameter 20 is retrieved from the device refresh parameter storage area 1271a on the shared memory 1271. The controller numbers 23 and 24 are read from the respective controllers 101 and 102, thus determining which one of the controllers is to receive the transmission data.

In step S1103, in order to transport the thus-prepared transmission data to another controller, the communicati_onsline 5e for protocol E common to the controllers is opened.

In step S1104, the write request transmission data that are completed are transmitted to the controller numbers 23 and 24 of the controllers 101 and 102.

After transmission of the write request transmission data has been completed, the communications line 5e for protocol E common to the controllers is closed in step S1105.

This completes transmission of the write request for writing device data of the controller to another controller.

Next, the operation of the write means 1275, which is for writing the device data write request data transmitted from another controller into the shared memory 1271 on the controller 100, will be described by reference to a flowchart shown in FIG. 29.

In step S1201, the device data write request data received f rom another controller are retrieved, and the number-of -device 27 is extracted from the thus-retrieved device data.

In step S1202, the device data write request data received from another controller are retrieved, and a destination on the 6 3% shred memory 1271 of the controller 100 where the device data are to be written is determined on the basis of the type- of-device 26 and the header-number-of-device 27. The device data 29 included in the received data are written into the device on the thus- determined shared memory 1271 in a number of times corresponding to the number of transported bytes.

In step S1203, a determination is made as to whether or not the device data corresponding to the number of data sets to be set have been written into the shared memory 1271. If all the data sets have been written, processing is terminated. In contrast, if not all the data sets have been written,- processing returns to step S1202, and the previously-described processing is performed.

This completes writing of the device data write request data received from another controller into the shared memory 1271 of the controller 100.

In addition.to the advantageous result yield by the third embodiment, the sixthembodiment yields an advantage of the ability to readily exchange data between the controllers connected by means of the same protocol.

Seventh Embodiment A seventh embodiment of the present invention, relating to a method of setting refresh parameter data, will now be described by reference to FIGS. 30 through 33.

Those reference numerals that are the same as those used in the previous embodiments are assigned to identical or corresponding elements.

FIG. 30 is a functional diagram showing the functions of refresh parameter data setting means which operates within 64 memory according to the present invention. In the drawing, reference numeral 121 designates a user program which accesses shared memory 1281 through use of standardized communications means. A userprogram 1211 for setting device refresh parameter data on the shared memory is provided within the user program 121. Reference numeral 128 designates data collection means which operates within the memory 120; 1281 designates shared memory which is provided within the data collection means 128 and where the device data retained by the PLC 4 are to be stored; 128le designates a storage area which is set within the shared memory and where device refresh parameter data are to be stored; 1282 designates shared memory data collection means which serves as data exchange means for exchanging device data between the shared memory and a specified user buffer; 1283 designates device refresh parameter data transfer means (hereinafter referred to as "transfer means") for transporting device refresh parameter data stored within the device refresh parameter storage area 1281e to the controller 101 or 102 by way of the second communications line; and 1284 designates write means which determines the type of data transmitted from another controller, writes the thus- received data into a device data storage area on the shared memory 1281 if the data correspond to device data, and writes the thus-received data into the device refresh parameter storage area 1281e if the data correspond to device refresh parameter data.

FIG. 31 is a flowchart showing the operation of the transfer means 1283; FIG. 32 is a flowchart showing the operation of the write means 1284; and FIG. 33 is a flowchart showing the operation of the user program for setting device refresh parameter data on the shared memory.

The operation of the refresh parameter data setting means will now be described.

First, the outline of operation of the refresh parameter data setting means will be described by reference to FIG. 30.

According to the user program 1211, device refresh parameter data are set on the device refresh parameter setting area 128le on the shared memory. The transfer means 1283 for transporting the device refresh parameter data to another controller is activated.

The transfer means 1283 reads the device refresh parameter (Jata from the device refresh parameter storage area 128le on the shared memory. On the basis of a communications protocol stored in advance in the transfer means 1283, the thus-read device refresh parameter data are transported to another controller. Upon receipt of the data from another controller, the write means 1284 determines whether or not the thus-received data are device data or device refresh parameter data. If the data are determined to be device data, the data are written into the device data storage area on the shared memory of the controller. In contrast, if the thus-received data are determined to be device refresh parameter data, the data are written into the device ref resh parameter storage area 128le on the shared memory of the controller.

Next, the operation of the transfer means 1283 for transporting device refresh parameter data to another controller will now be described by reference to a flowchart shown in FIG. 31.

The user buffer where the device refresh parameter data are stored and the device refresh parameter storage area on the 66 share memory are specified by the user program. As a result, by means of the shared memory data collection means 1282, the device refresh parameter data are transported from the user buffer to the device refresh parameter storage area 128le and set thereon.

In step S1301, the device refresh parameter data stored in the refresh parameter storage area 128le are read.

In step S1302, the communications protocol stored in the transfer means is read, and the communications line is opened in accordance with the thus-read communications protocol. The device refresh parameter data are transported to another controller connected to the controller by means of the same protocol.

As mentioned above, the device refresh parameter data set in the controller 100 can also be set to another controller such as the controller 101 or 102, in the same manner, by designation of the device refresh parameter storage area 128le and the user buffer where the device refresh parameter data are stored by the user program, through use of the transfer means.

The operation of the write means 1284 for writing the data read from another controller into the shared memory will now be described by reference to a flowchart shown in FIG. 32.

In step S1401, data are transported to the controller from another controller connected to the controller by means of the same protocol.

In step S1402, a determination is made as to whether or not the received data are device data or device refresh parameter data.

If in step S1402 the received data are determined to be device refresh parameter data, processing proceeds to step 67 S1403, where the received data are set in the device refresh parameter storage area 128le on the shared memory of the controller.

In contrast, if the received data are determined to be device data, processing proceeds to step S1404, where the received data are set in the device data storage area on the shared memory 1281 of the controller.

By means of the write means 1284, the received data can be written without use of the user program.

Next, the operation of the user program 1211, which sets the device refresh parameter data on the shared memory, will' be described by reference to a flowchart shown in FIG. 33.

In step S1501, device refresh parameter data to be stored on the refresh parameter storage area 128le are prepared.

In step S1502, refresh parameter data are set in the refresh parameter setting area 1281e, and the transfer means 1283 is activated.

The device refresh parameter data may be prepared as a user program. Alternatively, the user buffer where the device refresh parameter data are stored may be designated by means of the user program.

As has been described above, the present provides A data processor comprising:

communications protocol storage means for storing communications protocols assigned in advance to respective devices to be controlled, which are connected to the data processor by way of a communications line; device data processing means which collect device data retained by the device to be controlled or set device data on the device to be controlled, inaccordance with the 68 communications protocols stored in the communications protocol storage means; a shared memory region which stores the device data collected by the device data processing means or device data to be set on the device to be controlled; and data exchange means for exchanging the device data between the shared memory region and a designated user buffer. As a result, the only requirement of the user is that he be aware of the contents of the shared memory, and the user can collect and set device data device data from and on a plurality of PLCs assigned different communications protocols, by means ofstandardized procedures, without being aware of the use of different communications protocols. Further, a need for preparing a complicated user program is obviated, thus reducing a burden, which would otherwise be required by the user program.

Communication between the controller and the PLC is left to collection means,- and the user program performs only access to the shared memory, thereby yielding an improvement in the capability of the controller.

Particularly, the device data processing means has a refresh control function for collecting the device data retained by the device to be controlled or for setting device data to the device to be controlled, at predetermined timing. Therefore, the latest device data can be readily collected and set.

Further, the device data processing means reads predetermined timing, at which refresh control is effected, from a setting data file where data are set as parameters. Therefore, processing capability of the device data processing means with regard to processing based on parameters is improved, 69 and modification of setting values can be readily effected.

Further, the data exchange means exchanges all the data sets between the shared memory region and the designated user buffer, by communications means which are standardized in advance. Therefore, the user is only required to designate the user buffer and the shared memory location, and hence workability at the time of preparation of a user program is improved.

Further, the data exchange means exchange device data between the shared memory region and the user buffer, every time the value of the device data is changed. Accordingly, exchangeof data can be minimized.

Further, the shared memory region is divided into blocks for each device data set of the respective devices to be controlled, and device data are stored in the blocks. Accordingly, data can be readily handled.

Further, the present invention provides a data processing method comprising steps of:

reading communications protocols assigned to devices to be controlled, which are connected by way of a communications line, from communications protocol storage means where the communications protocols are stored for respective devices to be controlled; collecting device data retained by the devices to be controlled or setting device data in the devices to be controlled, by way of the communications line and in accordance with the read communications protocols; storing into a shared memory region the device data collected from the device to be controlled or device data to be set on the device to be controlled,; and exchanging the device data between the shared memory region and a designated user buffer. Therefore, the only requirement of the user is that he be aware of the contents of the shared memory, and the user can collect and set device data device data from and on a plurality of PLCs assigned different communications protocols, by means of standardized procedures, without being aware of the use of different communications protocols. Further, a need for preparing a complicated user program is obviated, thus reducing a burden, which would otherwise be required by the user program.

Further, communication between the controller and the-PLC' is left to collection means, and the user program performs only access to the shared memory, thereby yielding an improvement in the capability of the controller.

Further, the process of storing the device data collected from the device to be controlled or device data to be set on the device to be controlled, is performed at predetermined timing. Therefore, the latest device data can be re adily collected and set..

The present invention further provides a data processing system, in which controllers, each of which is connected by way of a first communications line to a device to be controlled, are connected together to, by way of a second communications line, wherein the controller comprises:

device data processing means which collects device data retained by the device to be controlled or sets device data on the device to be controlled, in accordance with the communications protocols assigned to the first communications line; 71 a shared memory region which stores the device data collected by the device data processing means or device data to be set on the device to be controlled; data exchange means for exchanging the device data between the shared memory region and a designated user buffer; second communication protocol storage means for storing, in advance, a communications protocol assigned to the second communications line; transmission means for transmitting the device data stored in the shared memory region by way of the second communications line in accordance with the communication-s protocol assigned to the second communications line stored in the second communications storage means; and write means for storing into the shared memory region the device data transmitted over the second communications line. Therefore, the only requirement of the user is that he be aware of the contents of the shared memory, and the user can collect and set device data device data from and on a plurality of PLCs assigned different communications protocols, by means of standardized procedures, without being aware of the use of different communications protocols. Further, a need for preparing a complicated user program is obviated, thus reducing a burden, which would otherwise be required by the user program.

Further, communication between the controller and the PLC is left to collection means, and the user program performs only access to the shared memory, thereby yielding an improvement in the capability of the controller.

Particularly, the data processing system further comprises first communications protocol storage means for storing first communications protocols assigned in advance to 12 respective devices to be controlled, which are connected to the data processing system by way of the first communications line. Therefore, a necessity for establishing a communications protocol by means of the user program is obviated, thereby preventing bloating of a program.

Further, the device data processing means has a refresh control function for collecting the device data retained by the device to be controlled or setting device data to the device to be controlled, at predetermined timing. Therefore, the latest device data can be readily collected and set among controllers..

Further, the transmission means transmits device data at predetermined timing by way of the second communications line, on the basis of the parameters stored in the shared memory region. Accordingly, refresh timing can be set as a parameter, and there can be readily achieved an improvement in processing capability of the data processor and easy modification of setting values.

Further, the transmission means operates at predetermined timing transmitted from activation means which operate according to predetermined parameters. Accordingly, transmission means operates at a predetermined timing at all times, and reliability of data is improved. Further, a necessity for setting timing by means of the-user program is obviated, thus preventing bloating of a program.

Further, the write means stores into the shared memory region the device data transmitted over the second communications line, while dividing the shared memory region into blocks that correspond to respective devicesAccordingly, handling of data is facilitated.

Since the second communications line is Ethernet protocol, 73 the degree of freedom of a system is increased.

Since parameters stored in the shared memory are transmitted by way of the second communications line, identical parameters can be readily set in the controllers connected over the second communications line, thereby improving efficiency of parameter setting, which have conventionally been performed by reconnection of peripheral devices.

Further, a determination is made as to whether or not the data transmitted over the second communications line are parameter or device data, and the data are stored into a parameter storage area on the shared memory region if the dataare determined to be parameter data, whereas the data are stored into one of storage areas provided for respective devices to be controlled if the data are determined to be device data. Therefore, data transmitted without involvement of setting by the user program can be arbitrarily classified and stored, thereby mitigating a burden imposed on the user.

-Industrial Applicability

As has been described above, the data processor, the data processing method, and the data processing system according to the present invention are suitable for use in collecting data from and setting data in PLCs or controllers connected by means of a predetermined communications protocol.

Cla s 1. A data processor comprising:

communications protocol storage means for storing communications protocols assigned in advance to respective devices to be controlled, which are connected to the data processor by way of a communications line; device data processing means which collect device data retained by the device to be controlled or set device data on the device to be controlled, in accordance with the communications protocols stored in the communications protocol storage means; a shared memory region which stores the device data collected by the device data processing means or device data to be set on the device to be controlled; and data exchange means for exchanging the device data between the shared memory region and a designated user buffer.

2. The data processor as defined in claim 1, wherein the device data processing means has a refresh control function for collecting the device data retained by the device to be controlled or for setting device data to the device to be controlled, at predetermined timing.

3. The data processor as defined in claim 2, wherein the device data processing means reads predetermined timing, at which refresh control is effected, from a setting data file where data are set as parameters.

4. The data processor as defined in claim 1, wherein the data exchange means exchanges all the data sets between the shared memory region and the designated user buffer, by communications means which are standardized in advance.

5. The data processor as defined in claim 1, wherein the data exchange means exchange device data between the shared memory region and the user buffer, every time the value of the device data is changed.

6. The data processor as defined in claim 1, wherein the shared memory region is divided into blocks for each device data set of the respective devices to be controlled, and device data are stored in the blocks.

7. A data processing method comprising steps of:

reading communications protocols assigned to devices to be controlled, which are connected by way of a communicationsline, from communications protocol storage means where the communications protocols are stored 'for respective devices to be controlled; collecting device data retained by the devices to be controlled or setting device data in the devices to be controlled, by way of the communications line and in accordance with the read communications protocols; storing into a shared memory region the device data collected from the device to be controlled or device data to be set on the device to be controlled,; and exchanging the device data between the shared memory region and a designated user buffer.

8. The data processing method as defined in claim 7, wherein the process of storing the device data collected from the device to be controlled or device data to be set on the device to be controlled, is performed at predetermined timing.

9. A data processing system, in which controllers, each of which is connected by way of a first communications line to a device to be controlled, are connected together to, by way 76 of a second communications line, wherein the controller comprises:

device data processing means which collects device data retained by the device to be controlled or sets device data on the device to be controlled, in accordance with the communications protocols assigned to the first communic ations line; a shared memory region which stores the device data collected by the device data processing means or device data to be set on the device to be controlled; data exchange means for exchanging the device databetween the shared memory region and a designated user buffer; second communication protocol storage means for storing, in advance, a communications protocol assigned to the second communications line; transmission means for transmitting the device data stored in the shared memory region by way of the second communications line in accordance with the communications protocol assigned to the second communications line stored in the second communications storage means; and write means for storing into the shared memory region the device data transmitted over the second communications line.

10. The data processing system as defined in claim 9, further comprising:

first communications protocol storage means for storing first communications protocols assigned in advance to respective devices to be controlled, which are connected to the data processing system by way of the first communications line.

11. The data processing system as defined in claim 9, wherein the device data processing means has a refresh control 77 function for collecting the device data retained by the device to be controlled or setting device data to the device to be controlled, at predetermined timing.

12. The data processing system as defined in claim 9, wherein the transmission means transmits device data at predetermined timing by way of the second communications line, on the basis of the parameters stored in the shared memory region.

13. The data processing system as defined in claim 12, wherein the transmission means operates at predetermined timing transmitted from activation means which operate according topredetermined parameters.

14. The data processing system as defined in claim 9, wherein the write means stores -into the shared memory region the device data transmitted over the second communications line, while dividing the shared memory region Into blocks that correspond to respective devices.

15. The data processing system as defined in claim 9, wherein the second communications line operates in accordance with Ethernet protocol.

16. The data processing system as defined in claim 9, wherein the parameters stored in the shared memory are transmitted over the second communications line.

17. The data processing system as defined in claim 16, wherein a determination is made as to whether or not the data transmitted over the second communications line are parameter or device data, and the data are stored into a parameter storage area on the shared memory region if the data are determined to be parameter data, whereas the data are stored into one of storage areas provided for respective devices to be controlled if the data are determined to be device data.

79