JP2003015705A - Network system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a network system including a programming device and a controller for allowing a programmer to execute communication programming among a plurality of controllers connected through a communication network without considering any address, and to easily describe data variable names or the like, and to display the generation of any communication abnormality among the controllers, and to set the behaviors of the controllers when the communication abnormality is generated. SOLUTION: In this network system in which a plurality of controller devices 200a and 200b are connected through a communication network to a programming device 300, the programming device is provided with a means for automatically allocating local memories in the respective controllers to data variable names to be added to input and output symbols for communication at the time of describing inter-controller communication, and the controllers are respectively provided with a means for making equivalent the allocated local memories through the network.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a controller device for communication programming between a plurality of controller devices connected by a communication network without the need for a programmer to be aware of the address, for easily describing a data variable name, etc. The present invention relates to a network system including a programming device and a controller device for displaying that a communication error has occurred between devices and setting the behavior of the controller device when the communication error occurs.

[0002]

2. Description of the Related Art In the prior art, for example, JP-A-9-12
As shown in Japanese Patent No. 8018, in communication programming in a multiprocessor system in which a common data memory coupled by a bus is shared by a plurality of processor devices, a data variable name is automatically assigned to a local memory in each processor device. Was possible.

[0003]

In the prior art, in communication programming in a multiprocessor system in which a common data memory coupled by a bus is shared by a plurality of processor devices, data variable names are assigned to local memory in each processor device. Although it was possible to automatically assign the data variable name to the local memory in each controller device, it was not possible to automatically assign the data variable name in the communication programming between a plurality of controller devices connected by the communication network.

The present invention has been made in order to solve the above problems, and in communication programming between a plurality of controller devices connected by a communication network, a programmer can perform programming without being aware of an address or data. A network system that includes a programming device and a controller device for easily describing variable names, displaying that a communication error has occurred between controller devices, and setting the behavior of the controller device when a communication error occurs. The purpose is to get.

[0005]

A network system according to the invention of claim 1 is a network system in which a plurality of controller devices and a programming device are connected by a communication network, and the programming device describes communication between the controller devices. In this case, a means for automatically allocating the local memory in each controller device to the data variable name given to the input / output symbol for communication is provided, and the controller device equivalences the allocated local memories via the network. It is equipped with a means to do.

A network system according to a second aspect of the present invention is the network system according to the first aspect, wherein the programming device, when inputting a data variable name of a communication input / output symbol, uses another controller device on the communication input side. Display the list of communication output data variable names already described in, and on the communication output side, display the list of communication input data variable names already described in the other controller device, and display the list. It is provided with a means for selecting a data variable name from the selected data.

A network system according to a third aspect of the present invention is the network system according to the first or second aspect, wherein the programming device displays a list of data variable names of communication input / output symbols already input to the program, In addition, a means for displaying is provided together with the device identification number of the controller device at the communication destination in which the communication input / output symbol with the data variable name is defined.

A network system according to a fourth aspect of the present invention is the network system according to the third aspect, wherein the programming device has a list of data variable names of communication input / output symbols already input to the program and the data variable names thereof. In addition to the device identification number of the controller device at the communication destination where the attached communication I / O symbol is defined, the identification number of the sheet where the communication I / O symbol with that data variable name is defined is displayed. It is equipped with a means to do.

A network system according to a fifth aspect of the present invention is the network system according to the fourth aspect, wherein the programming device identifies a sheet in which the communication input / output symbol is defined from the displayed data variable name list. It is provided with means for selecting a number and switching the display to that sheet.

A network system according to a sixth aspect of the present invention is the network system according to any one of the first to fifth aspects, wherein the programming device collectively sets the data variable names of the communication input / output symbols already input to the program. It is provided with a means for converting.

A network system according to a seventh aspect of the present invention is the network system according to any one of the first to sixth aspects, wherein the programming device has the same data among the data variable names of the output symbols for communication already described in the program. It is provided with a means for checking whether two or more variable names are defined.

According to an eighth aspect of the present invention, in the network system according to any one of the first to seventh aspects, the programming device includes means for defining a comment in a data variable name of a communication input / output symbol, and communication. A means for displaying the comment of the input / output symbol together with the data variable name is provided.

A network system according to a ninth aspect of the present invention is the network system according to the eighth aspect, wherein the programming device includes means for collectively converting the comments of the data variable names already described in the program. It is a thing.

According to a tenth aspect of the present invention, in the network system according to any one of the first to ninth aspects, the programming device is provided with the same communication data variable name near or inside the communication output symbol. Displays the device identification number of the controller device of the communication destination where the communication input symbol is defined, and the communication destination where the communication output symbol with the same communication data variable name is defined near or inside the communication input symbol. And a means for displaying the device identification number of the controller device.

According to an eleventh aspect of the present invention, in the invention of the tenth aspect, the programming device identifies a sheet in which a communication destination symbol is described in addition to the identification symbol of the communication destination controller device. It is provided with a means for displaying a number.

A network system according to a twelfth aspect of the present invention is the network system according to the eleventh aspect of the present invention, wherein the programming device includes means for switching the display to a sheet in which the symbol of the communication destination is described.

A network system according to a thirteenth aspect of the present invention is the network system according to any one of the first to twelfth aspects of the present invention, in which the programming device generates the same value previously generated in accordance with a change in a communication input / output symbol or a data variable name. It is provided with means for detecting whether there is a difference from the activation setting management table and displaying the result.

A network system according to a fourteenth aspect of the present invention is the network system according to any one of the first to thirteenth aspects, wherein the programming device sets the equivalence setting data in the programming device and the equivalence setting in each controller device. It is provided with a means for comparing the data and displaying whether there is a difference.

A network system according to a fifteenth aspect of the present invention is the network system according to any one of the first to fourteenth aspects, wherein the controller device is
It is provided with means for detecting the abnormality on the input side of the communication and for making the communication status of the input value abnormal when the communication abnormality is detected.

A network system according to a sixteenth aspect of the present invention is the network system according to the fifteenth aspect of the invention, wherein the programming device reads the communication status for the data in the work area of the controller device, and if the value is abnormal, it corresponds. The input symbols for communication are displayed in different colors.

A network system according to a seventeenth aspect of the present invention is the network system according to the fifteenth aspect, wherein, when a communication abnormality occurs, a data value before the communication abnormality occurs according to a preset mode. It is provided with a means for controlling whether to hold or change to a preset value.

A network system according to an eighteenth aspect of the present invention is the network system according to the sixteenth aspect of the present invention, wherein the programming device includes means for presetting behavior at the time of communication abnormality.

[0023]

BEST MODE FOR CARRYING OUT THE INVENTION Embodiment 1. Embodiment 1 of the present invention will be described below with reference to the drawings. 1 is a block diagram showing the configuration of the entire system according to Embodiment 1 of the present invention. In the figure, 100 is a communication network, 200a and 200b are controller devices, and 300 is a programming device. FIG. 2 is a block diagram showing the configuration of the controller device. In the figure, 201 is an equivalence means, 202 is a local memory, 203 is a work area in the local memory, 204 is an equivalence setting management table in the local memory, 205 is a program in the local memory, and 206 is a program execution means. .

FIG. 3 is a diagram showing the structure in the work area. An address is assigned to each data. FIG. 4 is a diagram showing a configuration in the equivalence setting management table. It is composed of an equivalence source device number, an equivalence source work address, and an equivalence destination work address. FIG. 5 is a block diagram showing the configuration of the programming device. In the figure, 301 is a data communication means, 302 is a data file, 303 is a work area management table stored in the data file, 304 is an equivalence setting management table stored in the data file, and 305 is stored in the data file. The created program, 306, is a programming means.

FIG. 6 is a diagram showing a description example of the inter-controller communication program. In the figure, 305a, 305
b is the described program, 400a is an output symbol for communication, 400b is an input symbol for communication, 401a, 40a
1b is a symbol for calculation, and 500a and 501b are data variable names. FIG. 7 is a diagram showing the structure of the work area management table. Here, the work area management table shown in FIG. 7A is for the controller device M1.
The work area management table shown in (b) is for the controller device M2. It consists of data variable name, input / output type, work area address, and usage flag. Figure 8
It is a figure which shows the structure of the equivalence setting management table. It is composed of an equivalence source device number, an equivalence source work address, and an equivalence destination work address.

Next, the operation will be described. First, the operation in the programming device will be described. In the programming device, as shown in FIG.
Programming is performed by connecting communication input / output symbols. When describing the inter-controller communication output, the communication output symbol (400a) is used. When describing inter-controller communication input, input symbol for communication (400
When communication is performed between controllers that assign data variable names to communication input / output symbols that use b), the same data variables are used for the communication output symbol (400a) and the communication input symbol (400b). Give a name.

The work area management table of FIG. 7 is prepared for each controller device. In the work address column in the work area management table, 0,
It is assumed that numbers in ascending order such as 1, 2, ... Are set.
The value 0 is set in the usage flag column in advance. From this initial state, when each communication input / output symbol is described for a certain controller device and a data variable name is given, the ones whose use flag is 0 in the work area management table are searched in order. , The data variable name is registered in the first place where 0 is set. At this time, at the same time, the input / output type (input or output) of each communication input / output symbol is registered in the input / output type, and the use flag is changed from 0 to 1. In this way, each time the input / output symbol for communication is described and the data variable name is given, the data variable name and input / output type are similarly registered in the work area management table, and the use flag is changed from 0 to 1. To change.

When all the programs have been written for each controller, the equivalence setting management table as shown in FIG. 8 is generated. Incidentally, the equivalence setting management table shown in FIG. 8 is for the controller device M2. This equivalence setting management table is generated as follows.

FIG. 9 is a flow chart showing the processing flow of the equivalence setting management table generation. First, in the work area management table of a controller device (M2), the data variable name of the input / output type = input is read (step ST01), and then
In the work area management table of the other controller device (M1 or the like), a data variable name that is read in step ST01 and has an input / output type = output is searched (step ST02), and then step The device number of the output side controller device (M1 or the like) retrieved in ST02 is written in the equivalence source device number of the equivalence setting management table (step ST03), and then the output side controller device (M1) retrieved in step ST02. Write the work address of the corresponding data variable name in (other) to the work area address of the equivalence source of the equivalence setting management table (step ST04), and finally, in the input side controller device (M2) searched in step ST01 Set the work address of the data variable name to the work area address of the equivalence destination of the equivalence setting management table. Write to (step ST05).
The above processing is repeated for each controller device until there is no corresponding data variable name, and the equivalence setting management table for each controller is generated. This equivalence setting management table is transmitted to each controller device and stored as an equivalence setting management table in the local memory.

Next, FIG. 10 for explaining the operation in the controller device is a flow chart showing the processing flow of the equivalencing means 201 (requesting side: the controller device M2 side in FIG. 6). First, the following steps are executed at regular intervals (step ST10). A local memory read request is transmitted to the device indicated by the equivalence source device number in the equivalence setting management table in order to read the value of the address indicated by the equivalence source work area address (step ST11), Next, a local memory read response is received from the equivalence source device (that is, the controller device M1 side in FIG. 6) (step ST12), and finally, the work address is indicated as the equivalence destination in the equivalence setting management table. The response data from the equivalence source device is written to the address in the device itself (step ST13).

On the other hand, FIG. 11 is a flow chart showing the processing flow of the equivalency setting means (response side). First,
A local memory read request is received (step ST2
0) Next, the value of the designated work address is read from the local memory in the own device (step ST2).
1) Finally, a local memory read response is transmitted to the request source device (step ST22).

As described above, according to this embodiment,
In the program for each controller written in the programming device, the work memory in the controller is automatically assigned to the communication input / output symbol with the data variable name, and the communication input / output with the same data variable name is assigned. An equivalence setting management table for equalizing symbols is generated, the equivalency setting management table is stored in each controller, and the equivalence processing is performed between the controller devices based on this equivalence setting management table. In the communication programming between the multiple controller devices connected by the communication network,
This has the effect that programmers can program without being aware of addresses.

Embodiment 2. The second embodiment of the present invention will be described below with reference to the drawings. FIG. 12 is a block diagram showing the configuration of the programming device. In the figure,
301 is a data communication means, 302 is a data file, 3
Reference numeral 03 is a work area management table stored in the data file, 304 is an equivalence setting management table stored in the data file, 305 is a program stored in the data file, 306 is programming means, 30
Reference numeral 7 is a data variable name list display means. FIG. 13 is a diagram showing an example of the inter-controller communication program already described. In the figure, 305c and 305d are written programs, 400c1 is a communication output symbol, and 400
c2 is an input symbol for communication, 400d is an output symbol for communication, 401c1, 401c2, 401d are symbols for calculation, and 500c1, 500c2, 500d are data variable names. FIG. 14 is a diagram showing an example of inputting a data variable name from a data variable name list screen in inter-controller communication programming.

FIG. 15 is a diagram showing the structure of the work area management table. Here, the work area management table shown in FIG. 15A is for the controller device M1,
The work area management table shown in FIG. 15B is for the controller device M2. Data variable name, POL type,
It consists of input / output type, work area address, and use flag. FIG. 16 is a diagram showing a data variable name list display (input). It consists of a data variable name and a controller device identification number.

Next, the operation of the programming device will be described. Similar to the operation of the first embodiment, when each communication input / output symbol is described and a data variable name is given to a certain controller device, the use flag in the work area management table becomes 0. The data variable names are registered for the first 0 part. At this time, at the same time,
Register the input / output type (input or output) of each communication input / output symbol, change the use flag from 0 to 1, and identify that the symbol is a communication input / output symbol in the POL type. In order to do so, a value indicating "communication POL" is set.

Next, the operation of the data variable name list display means 307 will be described. A description will be given based on the flowchart showing the data variable name list display processing flow of FIG. 17 as an example in which the program as shown in FIG. 14 is written in the state where the inter-controller communication program shown in FIG. 13 has already been written. To do. First, it is identified whether the communication input / output symbol is an input or an output (step ST30). In the case of an input symbol, the work area management table of each controller is then read (step ST31), and finally PO
For L type = communication POL and input / output type = output, a list of data variable names and controller device identification numbers is displayed (step ST32).

In the case of an output symbol in step ST30, next, the work area management table of each controller is read (step ST33), and finally, data variables for POL type = communication POL, input / output type = input The name and the identification number of the controller device are displayed in a list (step ST34). A required data variable name is selected from the data variable name list thus displayed, and the data variable name is assigned to the newly described communication input / output symbol.

As described above, according to this embodiment,
When newly describing the data variable name of the communication I / O symbol, refer to the list of data variable names of the communication I / O symbol already described in the program for each controller unit, together with the identification number of the controller unit. Since there is no need to directly input characters from a keyboard or the like, there is an effect that an input error is eliminated and an input work is made efficient.

Embodiment 3. Embodiment 3 of the present invention will be described below with reference to the drawings. FIG. 18 is a block diagram showing the configuration of the programming device. In the figure,
301 is a data communication means, 302 is a data file, 3
Reference numeral 03 is a work area management table stored in the data file, 304 is an equivalence setting management table stored in the data file, 305 is a program stored in the data file, 306 is programming means, 30
Reference numeral 9 is a data variable name list display means. FIG. 19 is a diagram showing a display example of a data variable name list in the case of an example of the inter-controller communication program of FIGS. 13 and 14 used in the description of the second embodiment.

Next, the operation of the data variable name list display means 309 in the programming device will be described. already,
It is assumed that the inter-controller communication program as shown in FIGS. 13 and 14 is described, and the description will be made based on the flowchart showing the data variable name list display processing flow in FIG. First, the work area management table of each controller is read (step ST40), and then the data variable name, the input / output type, and the identification number of the controller device are listed in a list for all those having POL type = communication POL. It is displayed (step ST41).

As described above, according to this embodiment,
Since a list of data variable names of communication input / output symbols already described in the program for each controller device is displayed together with the input / output type and the identification number of the controller device, which data variable is It is possible to easily confirm which controller device is used as an input or an output.

Fourth Embodiment Hereinafter, a fourth embodiment of the present invention will be described with reference to the drawings. FIG. 21 is a block diagram showing the configuration of the programming device. In the figure,
301 is a data communication means, 302 is a data file, 3
Reference numeral 03 is a work area management table stored in the data file, 304 is an equivalence setting management table stored in the data file, 305 is a program stored in the data file, 306 is programming means, 30
Reference numeral 9 is a data variable name list display means.

FIG. 22 is a diagram showing an example of the inter-controller communication program. In the figure, 305f, 305
g, 305h is the described program, 400f1, 4
00g is an output symbol for communication, 400f2, 400h are input symbols for communication, 401f1, 401f2, 401
g and 401h are calculation symbols, 500f1 and 500f
2,500 g and 500 h indicate data variable names.

FIG. 23 shows the structure of the work area management table. The work area management table shown in FIG. 23A is for the controller device M1.
The work area management table shown in FIG. 23 (b) is for the controller device M2, and the work area management table shown in FIG. 23 (c) is for the controller device M3. It is composed of a data variable name, POL type, input / output type, work area address, use flag, and sheet identification number.
FIG. 24 is a diagram showing a display example of a data variable name list. Data variable name, input / output type, controller device identification number,
It consists of the sheet identification number.

Next, the operation of the programming device will be described. Similar to the operation of the second embodiment, when each communication input / output symbol is described and a data variable name is given to a certain controller device, the use flag in the work area management table is 0. Items are searched in order, the data variable name and the input / output type (input or output) of each input / output symbol for communication are registered for the first 0, and the usage flag is changed from 0 to 1. Change, P
In addition to setting a value indicating "communication POL" in the OL type, the identification number of the sheet in which the communication input / output symbol and the data variable name are described is registered. The sheet identification number is a unique number in the controller device.

Next, the operation of the data variable name list display means 309 in the programming device will be described. already,
It is assumed that an inter-controller communication program as shown in FIG. 22 is described, and a description will be given based on the flowchart showing the data variable name list display processing flow in FIG. First, the work area management table of each controller is read (step ST50), and then POL type = communication P.
The data variable name, the input / output type, the controller device identification number, and the sheet identification number are displayed in a list for those that are OL (step ST51).

As described above, according to this embodiment,
Display a list of data variable names of communication I / O symbols already described in the program for each controller device, along with the I / O type, controller device identification number, and sheet identification number in which the data variable name is described. By doing so, it is possible to easily confirm which data variable is used as an input or output in which sheet of which controller device.

Embodiment 5. Embodiment 5 of the present invention will be described below with reference to the drawings. FIG. 26 is a block diagram showing the configuration of the programming device. In the figure,
301 is a data communication means, 302 is a data file, 3
Reference numeral 03 is a work area management table stored in the data file, 304 is an equivalence setting management table stored in the data file, 305 is a program stored in the data file, 306 is programming means, 30
9 is a data variable name list display means, 310 is a sheet selection /
It is a display means. The sheet selection / display means 310 is the data variable list display means 309 described in the fourth embodiment.
It is a means for selecting the sheet displayed in and displaying the selected sheet.

Next, the operation in the programming device will be described. The sheet displayed by the data variable list display means 309 described in the fourth embodiment is selected, and the selected sheet is displayed.

As described above, according to this embodiment,
Display a list of data variable names of communication I / O symbols already described in the program for each controller device, along with the I / O type, controller device identification number, and sheet identification number in which the data variable name is described. Since it is possible to display the selected sheet by selecting the sheet to be displayed, which data variable is used as an input or an output in which sheet of which controller device. While checking
There is an effect that a desired sheet can be selected and displayed.

Sixth Embodiment The sixth embodiment of the present invention will be described below with reference to the drawings. FIG. 27 is a block diagram showing the configuration of the programming device. In the figure,
301 is a data communication means, 302 is a data file, 3
Reference numeral 03 is a work area management table stored in the data file, 304 is an equivalence setting management table stored in the data file, 305 is a program stored in the data file, 306 is programming means, 31
Reference numeral 1 is a data variable name collective conversion means. FIG. 28 is a diagram showing the structure of the work area management table. here,
The work area management table shown in FIG. 28 (a) is for the controller device M1, and the work area management table shown in FIG. 28 (b) is for the controller device M3. It is composed of a data variable name, POL type, input / output type, work area address, and use flag.

Next, the operation of the data variable name batch conversion means 311 in the programming device will be described. FIG. 29
An explanation will be given based on the flowchart showing the data variable name batch conversion processing flow of. According to the data variable name before change (XXXX) and the data variable name after change (AAA) that are designated in advance, first, the work area management table of each controller is read (step ST60), and then,
The data variable name = data variable name before change (XXXX) is searched, and the data variable name is changed to the data variable name after change (AAAA) (step ST61).

As described above, according to this embodiment,
Since the data variable names of the communication input / output symbols already described in the program for each controller device are collectively converted, there is no need to open the corresponding sheets one by one and change the data variable names. There is an effect that the change work can be made efficient.

Embodiment 7. Embodiment 7 of the present invention will be described below with reference to the drawings. FIG. 30 is a block diagram showing the configuration of the programming device. In the figure,
301 is a data communication means, 302 is a data file, 3
Reference numeral 03 is a work area management table stored in the data file, 304 is an equivalence setting management table stored in the data file, 305 is a program stored in the data file, 306 is programming means, 31
2 is a data variable name double definition checking means.

FIG. 31 is a diagram showing an example of the inter-controller communication program. In the figure, 305i, 305
j, 305k is the described program, 400i1, 4
00j is an output symbol for communication, 400i2, 400k is an input symbol for communication, 401i1, 401i2, 401
j and 401k are calculation symbols, 500i1 and 500i
2,500j and 500k represent data variable names. Figure 32
FIG. 32 is a diagram showing a configuration of a work area management table in the case of using the inter-controller communication program shown in FIG. 31 as an example. Here, the work area management table shown in FIG. 32A is for the controller device M1.
The work area management table shown in (b) is for the controller device M2, and the work area management table shown in FIG. 32 (c) is for the controller device M3. It is composed of a data variable name, POL type, input / output type, work area address, use flag, and sheet identification number.

Next, the operation of the data variable name double definition checking means 312 in the programming device will be described. Description will be made based on the flowchart showing the data variable name double definition check processing flow in FIG. First, the work area management table of each controller is read (step ST70), and next, it is checked whether or not there is the same data variable name for all those having POL type = communication POL and input / output type = output. (Step ST7
1) Next, it is judged whether or not there is a double definition (step ST72). If there is no double definition, "no double definition" is displayed (step ST73). The defined data variable name, controller identification number, and sheet identification number are displayed (step ST7).
4).

As described above, according to this embodiment,
Check if there are multiple communication output symbols already described in the program for each controller device that have the same data variable name, and if there is, the data variable name, controller identification number, Since the sheet identification number is displayed, it is possible to easily detect an output symbol for communication that is erroneously double defined and prevent illegal communication.

Embodiment 8. Embodiment 8 of the present invention will be described below with reference to the drawing. FIG. 34 is a block diagram showing a configuration of a programming device. In the figure, 3
01 is a data communication means, 302 is a data file, 30
3 is a work area management table stored in the data file, 304 is an equivalence setting management table stored in the data file, 305 is a program stored in the data file, and 306 is a programming means.

FIG. 35 is a diagram showing an example of an inter-controller communication program. In the figure, 305i is a written program, 400i1 is a communication output symbol, and 40
0i2 is an input symbol for communication, 401i1, 401i2
Indicates a calculation symbol, 500i1 and 500i2 indicate data variable names, and 600i1 and 600i2 indicate comments. Figure 3
FIG. 6 is a diagram showing the structure of a work area management table when the inter-controller communication program shown in FIG. 35 is taken as an example. It is composed of a data variable name, a comment, a POL type, an input / output type, a work area address, and a use flag.

Next, a comment display operation in the programming means 306 in the programming device will be described. When each input / output symbol for communication is described for a certain controller device and a data variable name is given, a comment can be defined at the same time. Similar to the operation of the second embodiment, when the data variable name is registered in the work area management table, the ones in which the use flag is 0 are sequentially searched, and the first place is 0. , The data variable name, the input / output type (input or output) of each communication input / output symbol, and the POL type are “communication PO”.
In addition to setting a value indicating "L", the input comment is set. In the programming means 306,
When the communication input / output symbol is displayed, a comment is displayed in the vicinity of the place where the data variable name is displayed (for example, at the top as shown in FIG. 35).

As described above, according to this embodiment,
Since a comment is defined for the data variable name and the defined comment is displayed together with the data variable name, it is possible to describe what kind of communication is being performed as a comment in an easy-to-understand manner. It has the effect of increasing the possibility.

Ninth Embodiment The ninth embodiment of the present invention will be described below with reference to the drawings. FIG. 37 is a block diagram showing the configuration of the programming device. In the figure,
301 is a data communication means, 302 is a data file, 3
Reference numeral 03 is a work area management table stored in the data file, 304 is an equivalence setting management table stored in the data file, 305 is a program stored in the data file, 306 is programming means, 31
3 is a comment-bulk conversion means. FIG. 38 is a diagram showing the structure of the work area management table. It is composed of a data variable name, a comment, a POL type, an input / output type, a work area address, and a use flag.

Next, the operation of the comment-lump conversion means 313 in the programming device will be described. Description will be made based on the flowchart showing the comment-lump conversion processing flow in FIG. 39. The data variable name (XXX) specified in advance
X), according to the comment after the change (comment'XXXX '), first, the work area management table of each controller is read (step ST75), and then the data variable name = the specified data variable name. The comment is changed to the comment after the change (comment 'of XXXX') (step ST76).

As described above, according to this embodiment,
Since the comments for the data variables of the communication input / output symbols already described in the program for each controller device are collectively converted, there is no need to open the corresponding sheets one by one and change the comments. This has the effect of making the change work more efficient and reducing input errors.

Embodiment 10. The tenth embodiment of the present invention will be described below with reference to the drawings. FIG. 40 is a block diagram showing the configuration of the programming device. In the figure, 301 is a data communication means, 302 is a data file, 303 is a work area management table stored in the data file, 304 is an equivalence setting management table stored in the data file, and 305 is stored in the data file. The created program, 306, is a programming means.

FIG. 41 is a diagram showing an example of an inter-controller communication program. In the figure, 305m, 305n
Is a written program, 400m is an output symbol for communication, 400n is an input symbol for communication, 401m, 401
n is a symbol for calculation, 500m and 500n are data variable names, and 700m and 700n are controller device numbers. FIG. 42 is a diagram showing the structure of the work area management table. Here, the work area management table shown in FIG. 42A is for the controller device M1.
The work area management table shown in (b) is for the controller device M3. It is composed of a data variable name, POL type, input / output type, work area address, use flag, and sheet identification number.

Next, the operation of displaying the device identification number in the programming means 306 in the programming device will be described. Description will be made based on the flowchart showing the device identification number display processing flow of FIG. First, it is identified whether the communication input / output symbol is an input or an output (step ST8).
0). If it is an input symbol, then the work area management table of each controller is read (step ST8).
1) Next, for the POL type = communication POL and the input / output type = output, the data variable names that match are searched, and if there is a match, the identification number of the controller device is input for communication. It is displayed near or inside the symbol (inside in the example of FIG. 41) (step ST82). In the case of an output symbol in step ST80, the work area management table of each controller is read next (step ST83), and finally, for the one of POL type = communication POL and input / output type = input, the data variable name is one. If there is a match, the identification number of the controller device is displayed near or inside the communication output symbol (inside in the example of FIG. 41) (step ST8).
4).

As described above, according to this embodiment,
Since the controller device identification number of the communication destination is displayed near or inside the input / output symbol for communication described in the program, it is possible to prevent the communication destination controller from being described incorrectly. Further, there is an effect that the work of following the processing flow of the program including the communication between the controllers can be made efficient.

Eleventh Embodiment The eleventh embodiment of the present invention will be described below with reference to the drawings. FIG. 44 is a block diagram showing the configuration of the programming device. In the figure, 301 is a data communication means, 302 is a data file, 303 is a work area management table stored in the data file, 304 is an equivalence setting management table stored in the data file, and 305 is stored in the data file. The created program, 306, is a programming means. FIG. 45 is a diagram showing an example of an inter-controller communication program. In the figure, 305p and 305q are written programs, 400p is an output symbol for communication,
400q is a communication input symbol, 401p and 401q are calculation symbols, 500p and 500q are data variable names,
700p and 700q are controller device numbers, 800
p and 800q are sheet identification numbers. FIG. 46 is a diagram showing the structure of the work area management table. here,
The work area management table shown in FIG. 46A is for the controller device M1, and the work area management table shown in FIG. 46B is for the controller device M3. It is composed of a data variable name, POL type, input / output type, work area address, use flag, and sheet identification number.

Next, the operation of displaying the device identification number and sheet identification number in the programming means 306 in the programming device will be described. The device identification number of FIG. 47,
An explanation will be given based on a flowchart showing a sheet identification number display processing flow. First, it is identified whether the communication input / output symbol is an input or an output (step ST90). In the case of an input symbol, next, the work area management table of each controller is read (step ST91), and then the POL type = communication POL, the input / output type = output, the data variable names of which match each other. If there is a match, the identification number and sheet identification number of the controller device are displayed near or inside the communication input symbol (inside in the example of FIG. 45) (step ST92). In the case of an output symbol in step ST90, the work area management table of each controller is then read (step ST93), and finally, for the POL type = communication POL and the input / output type = input, the data variable name is one. If there is a match, the identification number and the sheet identification number of the controller device are displayed near or inside the communication output symbol (inside in the example of FIG. 45) (step ST94).

As described above, according to this embodiment,
Since the controller device identification number and sheet identification number of the communication destination are displayed near or inside the communication input / output symbol described in the program, it is possible to prevent incorrect description of the communication destination controller. Further, there is an effect that the work of confirming the program content can be made more efficient by following the processing flow of the program including inter-controller communication.

Twelfth Embodiment The twelfth embodiment of the present invention will be described below with reference to the drawings. FIG. 48 is a block diagram showing the configuration of the programming device. In the figure, 301 is a data communication means, 302 is a data file, 303 is a work area management table stored in the data file, 304 is an equivalence setting management table stored in the data file, and 305 is stored in the data file. The created program, 306 is programming means, and 314 is sheet display switching means.

Next, the operation of the programming device will be described. When the operator designates a communication input / output symbol with a mouse or the like and gives a sheet switching instruction, the sheet display switching means 314 displays the controller device identification number and the sheet identification number described in the eleventh embodiment. Switch the display to the created sheet.

As described above, according to this embodiment,
The controller device identification number and sheet identification number of the communication destination are displayed near or inside the communication I / O symbol described in the program, and the operator specifies the communication I / O symbol with a mouse or the like. Since it is possible to switch to the displayed sheet, there is an effect that the work of confirming the program contents can be made more efficient by following the processing flow of the program including inter-controller communication.

Thirteenth Embodiment The thirteenth embodiment of the present invention will be described below with reference to the drawings. FIG. 49 is a block diagram showing the configuration of the programming device. In the figure, 301 is a data communication means, 302 is a data file, 303 is a work area management table stored in the data file, 304 is an equivalence setting management table stored in the data file, and 305 is stored in the data file. The created program, 306 is programming means, and 315 is an equivalence setting management table comparison means.
FIG. 50 is an example of an inter-controller communication program. In the figure, 305r, 305s, and 305t are written programs, 400r and 400s are communication output symbols, 400t is communication input symbols, and 401.
r, 401s, 401t are calculation symbols, 500r,
500s, 500t1 and 500t2 represent data variable names.

FIG. 51 is a diagram showing the structure of a work area management table when the inter-controller communication program of FIG. 50 is taken as an example. FIG. 23 is a diagram showing the structure of the work area management table. Here, the work area management table shown in FIG. 51A is the controller device M1.
The work area management table shown in FIG. 51 (b) is for the controller device M2, and the work area management table shown in FIG. 51 (c) is for the controller device M3. It is composed of a data variable name, POL type, input / output type, work area address, use flag, and sheet identification number. FIG. 52 is a diagram showing an equivalence setting management table for the controller device M3 when the inter-controller communication program of FIG. 50 is taken as an example.

Next, the operation of the programming device will be described. In the program (305t) of the controller device M3 of FIG. 50, the data variable name of the communication input symbol is set to “XXXX” (before change), and the programs (305r, 305s) of the controller devices M1 and M2 are as shown in FIG. It shall be described. In this state, the equivalence setting management table is generated according to the processing flow described in FIG. 9 of the first embodiment.

Next, in the program (305t) of the controller M3 of FIG. 50, the data variable names of the communication input symbols are changed from "XXXX" (before change) to "YYY".
An example will be described in the case of changing to "Y" (after change). In this state, when the equivalence setting management table is generated according to the processing flow described in FIG. 9 of the first embodiment, as shown in FIG. 52, the contents of the equivalence setting management table different from those of the equivalence setting management table generated before the change are generated. A table is created. The equivalence setting management table comparison means 315 compares the last generated equivalency setting management table with the equivalence setting management table generated from the latest work area management table, and in both of them, the equivalence source device number, If either the equivalence source work area address or the equivalence destination work area address is different, the difference is displayed.

As described above, according to this embodiment,
Since it is possible to compare the previously generated equivalency setting management table and the equivalency setting management table generated from the latest work area management table, the equivalency setting management table can be changed as the communication input / output symbol or data variable name is changed. There is an effect that it is possible to easily detect that the is changed.

Fourteenth Embodiment The fourteenth embodiment of the present invention will be described below with reference to the drawings. FIG. 53 is a block diagram showing the configuration of the programming device. In the figure, 301 is a data communication means, 302 is a data file, 303 is a work area management table stored in the data file, 304 is an equivalence setting management table stored in the data file, and 305 is stored in the data file. The created program, 306 is a programming means, and 316 is an equivalence setting management table comparison means.

Next, the operation of the programming device will be described. According to the processing flow described in FIG. 9 of the first embodiment, after generating the equivalence setting management table, the equivalence setting management table is transmitted to each controller device. The equivalence setting management table comparison means 316 reads the equivalence setting table in each controller device, compares it with the equivalence setting management table in the programming device, and compares the equivalence source device number and the equivalence source work between them. If either the area address or the work area address for equivalence is different, the difference is displayed.

As described above, according to this embodiment,
Since it is now possible to compare the equivalency setting management table in each controller device with the equivalence setting management table in the programming device, after generating the equivalency setting management table, sending it to each controller device and then for communication The equivalence setting management table was changed due to the change of the input / output symbol and the data variable name, and the equivalence setting management table in each controller device and the latest equivalence setting management table in the programming device did not match. This has the effect that it can be easily detected.

Fifteenth Embodiment The fifteenth embodiment of the present invention will be described below with reference to the drawings. FIG. 54 is a block diagram showing the configuration of the controller device. In the figure, 207 is an equivalence and communication error detection means, 202 is a local memory, 203 is a work area in the local memory, 204 is an equivalence setting management table in the local memory, 205 is a program in the local memory, 206
Is a program execution means. FIG. 55 is a diagram showing the configuration in the work area. It consists of data and communication status, and an address is assigned to each data. FIG. 56 is a diagram showing the structure of the equivalence setting management table. It is composed of an equivalence source device number, an equivalence source work address, and an equivalence destination work address.

Next, the operation in the controller device will be described. FIG. 57 is a flowchart showing the processing flow of the equivalency setting means (requesting side). First, the following steps are executed at regular intervals (step ST100). A local memory read request is transmitted to the device indicated by the equivalence source device number in the equivalence setting management table in order to read the value of the address indicated by the equivalence source work area address (step ST101).

Next, it is determined whether a communication error has occurred (step ST102). In step ST102, if there is no communication error and a response is received normally, then the response from the equivalence source device is sent to the address in the self device indicated by the work address in the equivalence setting management table. Write the data. At the same time, 0 (normal) is written in the communication status (step ST103). In step ST102, if a communication error occurs,
1 (abnormal) is written in the communication status of the address in the own device indicated by the work address in the equivalence destination of the equivalence setting management table (step ST104). The processing flow of the equivalence setting means (responding side) is the same as in the first embodiment.
11 is similar to the flowchart shown in FIG.

As described above, according to this embodiment,
The work area in the controller device has a communication status for each data, and the communication error is detected by the equalization and communication error detection means. When a communication error occurs, the communication status of the corresponding data is abnormal. Value is written, and if communication is performed normally, a value indicating normality is written in the communication status of the corresponding data. For example, the programming device should read the communication status together with the data. Thus, it is possible to easily confirm whether or not the communication is normally performed.

Sixteenth Embodiment The sixteenth embodiment of the present invention will be described below with reference to the drawings. FIG. 58 is a block diagram showing the configuration of the programming device. In the figure, 301 is a data communication means, 302 is a data file, 303 is a work area management table stored in the data file, 304 is an equivalence setting management table stored in the data file, and 305 is stored in the data file. The created program, 306 is programming means, and 317 is monitoring means. FIG. 59 is a diagram showing a monitor display example of an inter-controller communication program. In the figure, 305u and 305v are written programs, 400u is an output symbol for communication, 400v is an input symbol for communication, 401u and 401v are operation symbols,
500u and 501v show data variable names. The controller device has the configuration shown in the fifteenth embodiment.

Next, the operation of the programming device will be described. The monitor means 317 obtains a work area address from the work area management table for the data variable name assigned to the communication input / output symbol in the currently displayed program, and the address is given to the controller device. Data and its communication status are read out through the data communication means 301. At this time, the color of the communication input / output symbol is displayed differently depending on whether the read communication status is a normal value or an abnormal value.
(For example, black for normal value, red for abnormal value.)

As described above, according to this embodiment,
When a program is monitored and displayed on the programming device, it corresponds to the monitored data variable name,
The communication status is read at the same time as the data in the work area in the controller device, and the color of the communication input / output symbol is changed and displayed according to the value of the communication status. There is an effect that can be easily confirmed.

Seventeenth Embodiment Hereinafter, a seventeenth embodiment of the present invention will be described with reference to the drawings. FIG. 60 is a block diagram showing a configuration of a controller device. In the figure,
207 is an equivalence and communication error detection means, 202 is a local memory, 203 is a work area in the local memory, 204 is an equivalence setting management table in the local memory, 205 is a program in the local memory, and 206 is a program execution means. is there. FIG. 61 is a diagram showing the structure in the work area. It consists of data and communication status, and an address is assigned to each data. Figure 6
2 is a diagram showing the configuration of the equivalence setting management table.
It is composed of an equivalence source device number, an equivalence source work address, an equivalence destination work address, a mode, and a fixed value.

FIG. 64 is a block diagram showing the structure of the programming device. In the figure, 301 is a data communication means, 302 is a data file, 303 is a work area management table stored in the data file, 304 is an equivalence setting management table stored in the data file, and 305 is stored in the data file. The designated program, 306 is programming means, and 318 is behavior setting means at the time of communication abnormality.

First, the operation in the controller device will be described. FIG. 63 is a flowchart showing the processing flow of the equivalency setting means (requesting side). First, the following steps are executed at regular intervals (step ST110). A local memory read request is transmitted to the device indicated by the equivalence source device number in the equivalence setting management table in order to read the value of the address indicated by the equivalence source work area address (step ST111). Next, it is determined whether a communication error has occurred (step ST11).
2). In step ST112, if there is no communication error and a response is received normally, then the response from the equivalence source device is sent to the address in the own device indicated by the work address in the equivalence setting management table. Write the data. At the same time, 0 (normal) is written in the communication status (step ST113).

If a communication error occurs in step ST112, then the mode is maintained at the previous value (mode =
It is determined whether it is 0) (step ST114). In step ST114, if the previous value is held, 1 (abnormal) is written in the communication status of the address in the own device indicated by the work address in the equivalence setting management table (step ST115). In step ST114, when the previous value is not held (when mode = 1), a fixed value is written in the data area of the address in the own device indicated by the work address in the equivalence setting management table, and communication is performed simultaneously. Write 1 (abnormal) in the status (step ST116). The processing flow of the equivalence setting means (responding side) is the same as in FIG.
It is similar to the flowchart shown in FIG.

Next, the operation in the programming device will be described. Mode (0 ... previous value holding mode, 1 ... fixed value mode) and fixed value are added to the equivalence setting management table generated by the communication abnormal behavior setting means 318 according to the flow shown in FIG. 9 of the first embodiment. To set. Also,
The equivalence setting management table set here is transmitted to each controller device through the data communication means.

As described above, according to this embodiment,
By the communication error behavior setting means in the programming device, whether to hold the value before the communication error when communication error occurs or whether to set a certain fixed value, and set the fixed value and set the equivalency setting management The table is sent to the controller device, and in the controller device, when a communication error occurs, the value before the communication error is set according to the mode in the equivalency setting management table set and stored in this way. Since it is determined whether to hold or write a fixed value, there is an effect that it is possible to realize a communication process that can flexibly cope with a communication error.

[0096]

As described above, according to the present invention, in the program for each controller device written in the programming device, the work memory in the controller device is applied to the communication input / output symbol with the data variable name. Is automatically assigned, and an equivalence setting management table for equalizing communication input / output symbols with the same data variable name is generated, and the equivalency setting management table is stored in each controller device. Between controller devices,
Since the equivalence processing is executed based on this equivalence setting management table, there is an effect that the programmer can perform programming without being aware of the address in communication programming between a plurality of controller devices connected by the communication network. .

When newly describing the data variable name of the communication input / output symbol, a list of the data variable names of the communication input / output symbol already described in the program for each controller device is displayed in the controller device. Since it can be referred to and described together with the identification number, there is no need to directly input a character from a keyboard or the like, and there is an effect that an input error is eliminated and an input work is made efficient.

Since the list of the data variable names of the communication input / output symbols already described in the program for each controller device is displayed together with the input / output type and the controller device identification number, It is possible to easily confirm which data variable is used as an input or an output in which controller device.

In addition, a list of the data variable names of the communication input / output symbols already described in the program for each controller device is displayed on the sheet in which the input / output type, the controller device identification number and the data variable name are described. It is possible to easily confirm which data variable is used as an input or an output on which sheet of which controller device, since the data is displayed together with the identification number.

In addition, a list of the data variable names of the communication input / output symbols already described in the program for each controller device is described in the sheet in which the input / output type, the controller device identification number and the data variable name are described. Since it is displayed together with the identification number of, the sheet to be displayed can be selected and the selected sheet can be displayed, which data variable is input or output in which sheet of which controller device There is an effect that you can select and display the sheet you want to see while checking whether it is used as

Further, since the data variable names of the communication input / output symbols already described in the program for each controller device are collectively converted, the corresponding sheet is opened one by one and the data variable name is changed. There is no need to change, and there is an effect that change work can be made efficient.

Also, it is checked whether or not there are a plurality of communication output symbols already described in the program for each controller device, which have the same data variable name. Since the controller identification number and the sheet identification number are displayed, it is possible to easily detect an output symbol for communication that is erroneously double defined and prevent illegal communication.

Further, since a comment is defined for the data variable name and the defined comment is displayed together with the data variable name, it is possible to easily describe what kind of communication is being performed as a comment. , It is effective in improving the readability of the communication program.

Further, since the comments for the data variables of the communication input / output symbols already described in the program for each controller device are collectively converted, the comments are changed by opening the corresponding sheets one by one. There is an effect that the change work can be made efficient and input mistakes can be reduced.

Further, since the identification number of the controller device of the communication destination is displayed near or inside the input / output symbol for communication described in the program, it is possible to describe the communication destination controller by mistake. In addition, there is an effect that the work of following the processing flow of the program including inter-controller communication can be made efficient.

Further, since the identification number and the sheet identification number of the communication destination controller device are displayed near or inside the communication input / output symbol described in the program, the communication destination controller device is incorrect. Therefore, there is an effect that it is possible to prevent the description from occurring in advance, and the efficiency of the work of confirming the program contents by following the processing flow of the program including the communication between the controller devices.

Further, the identification number and the sheet identification number of the controller device of the communication destination are displayed near or inside the input / output symbol for communication described in the program, and the operator inputs it for communication with a mouse or the like. Since the output symbol can be designated and switched to the displayed sheet, there is an effect that the work of confirming the program content can be efficiently performed by following the processing flow of the program including the communication between the controller devices.

Further, since the previously generated equivalence setting management table and the latest equivalency setting management table can be compared, the communication input / output symbol and the data variable name are changed. It is possible to easily detect that the equivalence setting management table has been changed.

Further, since the equivalence setting management table in each controller device and the equivalence setting management table in the programming device can be compared with each other, the equivalence setting management table is generated and then transmitted to each controller device. After that, the equivalence setting management table is changed with the change of the communication input / output symbol and the data variable name, and the equivalence setting management table in each controller device and the latest equivalence setting management table in the programming device are changed. There is an effect that it is possible to easily detect that there is a mismatch.

Further, the work area in the controller device is provided with a communication status for each data, and the communication error is detected by the equalization and communication error detecting means,
When a communication error occurs, a value indicating an abnormality is written to the communication status of the corresponding data, and when communication is performed normally, a value indicating normal is written to the communication status of the corresponding data. For example, by reading the communication status together with the data with the programming device, it is possible to easily confirm whether or not the communication is normally performed.

When a programming device monitors and displays a certain program, the communication status is read at the same time as the data in the work area in the controller device corresponding to the monitored data variable name. Since the color of the communication input / output symbol is changed and displayed depending on the value of the communication status, it is possible to easily confirm whether or not the communication is normally performed.

Further, the behavior setting means at the time of communication abnormality in the programming device sets and sets a mode in which a value before the communication error is held at the time of communication abnormality or a fixed value is set, and a fixed value is set. Since the same equivalence setting management table is transmitted to the controller device, there is an effect that it is possible to realize a communication process that can flexibly cope with a communication abnormality.

In the controller device, according to the mode in the equivalency setting management table set and stored in the programming device, when a communication error occurs, the value before the communication error is retained or a fixed value is set. Since it is determined whether or not to write in, there is an effect that it is possible to realize a communication process that can flexibly cope with the occurrence of a communication abnormality.

[Brief description of drawings]

FIG. 1 is a block diagram showing a configuration of an entire system according to a first embodiment of the present invention.

FIG. 2 is a block diagram showing a configuration of a controller device according to the first embodiment of the present invention.

FIG. 3 is a diagram showing a configuration in a work area in the controller device according to the first embodiment of the present invention.

FIG. 4 is a diagram showing a configuration of an equivalence setting management table in the controller device according to the first embodiment of the present invention.

FIG. 5 is a block diagram showing a configuration of a programming device according to the first embodiment of the present invention.

FIG. 6 is a diagram showing a description example of an inter-controller communication program according to the first embodiment of the present invention.

7A is a diagram showing a work area management table for the controller device M1 in the programming device according to the first embodiment of the present invention, and FIG. 7B is a programming diagram according to the first embodiment of the present invention. It is a figure which shows the work area management table for controller apparatuses M2 in an apparatus.

FIG. 8 is a diagram showing an equivalence setting management table for the controller device M2 in the programming device according to the first embodiment of the present invention.

FIG. 9 is a flowchart showing an operation of processing for generating an equivalence setting management table in the programming device according to the first embodiment of the present invention.

FIG. 10 is a flow chart showing the operation of the equivalving means (requesting side) in the controller device according to the first embodiment of the present invention.

FIG. 11 is a flowchart showing the operation of the equivalencing means (response side) in the controller device according to the first embodiment of the present invention.

FIG. 12 is a block diagram showing a configuration of a programming device according to a second embodiment of the present invention.

FIG. 13 is a diagram showing a description example of an inter-controller communication program already described according to the second embodiment of the present invention.

FIG. 14 is a diagram showing an example of an input screen from a data variable name list screen in the inter-controller communication program according to the second embodiment of the present invention.

FIG. 15 (a) is a controller device M in a programming device according to a second embodiment of the present invention.
15 is a diagram showing a work area management table for No. 1, FIG.
FIG. 11B is a diagram showing a work area management table for the controller device M2 in the programming device according to the second embodiment of the present invention.

FIG. 16 is a diagram showing a display example of a data variable name list in the programming device according to the second embodiment of the present invention.

FIG. 17 is a flowchart showing an operation of data variable name list display processing in the programming device according to the second embodiment of the present invention.

FIG. 18 is a block diagram showing a configuration of a programming device according to a third embodiment of the present invention.

FIG. 19 is a diagram showing a display example of a list of data variable names in the programming device according to the third embodiment of the present invention.

FIG. 20 is a flowchart showing an operation of a data variable name list display process in the programming device according to the third embodiment of the present invention.

FIG. 21 is a block diagram showing a configuration of a programming device according to a fourth embodiment of the present invention.

FIG. 22 is a diagram showing a description example of an inter-controller communication program according to the fourth embodiment of the present invention.

FIG. 23 (a) is a controller device M in a programming device according to a fourth embodiment of the present invention.
23 is a diagram showing a work area management table for No. 1, FIG.
23B is a diagram showing a work area management table for the controller device M2 in the programming device according to the fourth embodiment of the present invention, and FIG. 23C is a controller device M3 in the programming device according to the fourth embodiment of the present invention. It is a figure which shows the work area management table for.

FIG. 24 is a diagram showing a display example of a list of data variable names in the programming device according to the fourth embodiment of the present invention.

FIG. 25 is a flowchart showing an operation of data variable name list display processing in the programming device according to the fourth embodiment of the present invention.

FIG. 26 is a block diagram showing a configuration of a programming device according to a fifth embodiment of the present invention.

FIG. 27 is a block diagram showing a configuration of a programming device according to a sixth embodiment of the present invention.

FIG. 28 (a) is a controller device M in a programming device according to a sixth embodiment of the present invention.
28 is a diagram showing a work area management table for 1;
FIG. 16B is a diagram showing a work area management table for the controller device M3 in the programming device according to the sixth embodiment of the present invention.

FIG. 29 is a flowchart showing an operation of a data variable name batch conversion process in the programming device according to the sixth embodiment of the present invention.

FIG. 30 is a block diagram showing the configuration of a programming device according to a seventh embodiment of the present invention.

FIG. 31 is a diagram showing a description example of an inter-controller communication program according to the seventh embodiment of the present invention.

32A is a diagram showing a work area management table for the controller device M1 in the programming device according to the seventh embodiment of the present invention, and FIG. 32B is a view showing the work area management table in the programming device according to the seventh embodiment of the present invention. FIG. 32C is a diagram showing a work area management table for the controller device M2, and FIG.
5 is a diagram showing a work area management table for the controller device M3 in the programming device according to FIG.

FIG. 33 is a flowchart showing the operation of a data variable name double definition check process in the programming device according to the seventh embodiment of the present invention.

FIG. 34 is a block diagram showing the structure of a programming device according to an eighth embodiment of the present invention.

FIG. 35 is a diagram showing a description example of an inter-controller communication program according to the eighth embodiment of the present invention.

FIG. 36 is a diagram showing a work area management table for the controller device M1 in the programming device according to the eighth embodiment of the present invention.

FIG. 37 is a block diagram showing the structure of a programming device according to a ninth embodiment of the present invention.

FIG. 38 is a diagram showing a work area management table for the controller device M1 in the programming device according to the ninth embodiment of the present invention.

FIG. 39 is a flowchart showing the operation of a comment-lump conversion process in the programming device according to the ninth embodiment of the present invention.

FIG. 40 is a block diagram showing the structure of a programming device according to a tenth embodiment of the present invention.

FIG. 41 is a diagram showing a description example of an inter-controller communication program according to the tenth embodiment of the present invention.

FIG. 42 (a) is a tenth embodiment of the present invention.
42 shows a work area management table for the controller device M1 in the programming device according to FIG.
(B) is a diagram showing a work area management table for the controller device M3 in the programming device according to the tenth embodiment of the present invention.

FIG. 43 is a flowchart showing an operation of controller device identification number display processing in the programming device according to the tenth embodiment of the present invention.

FIG. 44 is a block diagram showing the structure of a programming device according to an eleventh embodiment of the present invention.

FIG. 45 is a diagram showing a description example of an inter-controller communication program according to the eleventh embodiment of the present invention.

FIG. 46 (a) shows an eleventh embodiment of the present invention.
46 shows a work area management table for the controller device M1 in the programming device according to FIG.
(B) is a diagram showing a work area management table for the controller device M3 in the programming device according to the eleventh embodiment of the present invention.

FIG. 47 is a flowchart showing the operation of controller device identification number / sheet identification number display processing in the programming device according to the eleventh embodiment of the present invention.

FIG. 48 is a block diagram showing the structure of a programming device according to a twelfth embodiment of the present invention.

FIG. 49 is a block diagram showing the structure of a programming device according to a thirteenth embodiment of the present invention.

FIG. 50 is a diagram showing a description example of an inter-controller communication program according to the thirteenth embodiment of the present invention.

FIG. 51 (a) shows a thirteenth embodiment of the present invention.
51 shows a work area management table for the controller device M1 in the programming device according to FIG.
51B is a diagram showing a work area management table for the controller device M2 in the programming device according to the thirteenth embodiment of the present invention, and FIG. 51C is a controller device M3 in the programming device according to the thirteenth embodiment of the present invention. It is a figure which shows the work area management table for.

FIG. 52 is a diagram showing an equivalence setting management table for the controller device M3 in the programming device according to the thirteenth embodiment of the present invention.

FIG. 53 is a block diagram showing the structure of a programming device according to a fourteenth embodiment of the present invention.

FIG. 54 is a block diagram showing the structure of a controller device according to a fifteenth embodiment of the present invention.

FIG. 55 is a diagram showing the structure of the work area in the controller device according to the fifteenth embodiment of the present invention.

FIG. 56 is a diagram showing a structure of an equivalence setting management table in a controller device according to a fifteenth embodiment of the present invention. '

FIG. 57 is a flowchart showing the operation of the equivalencing means (requesting side) in the controller device according to the fifteenth embodiment of the present invention.

FIG. 58 is a block diagram showing the structure of a programming device according to a sixteenth embodiment of the present invention.

FIG. 59 is a diagram showing a monitor display example of an inter-controller communication program according to the sixteenth embodiment of the present invention.

FIG. 60 is a block diagram showing the structure of a controller device according to a seventeenth embodiment of the present invention.

FIG. 61 is a diagram showing the structure of the work area in the controller device according to the seventeenth embodiment of the present invention.

FIG. 62 is a diagram showing a structure of an equivalence setting management table in a controller device according to a seventeenth embodiment of the present invention.

FIG. 63 is a flowchart showing the operation of the equivalencing means (requesting side) in the controller device according to the seventeenth embodiment of the present invention.

FIG. 64 is a block diagram showing the structure of a programming device according to a seventeenth embodiment of the present invention.

FIG. 65 is a diagram showing a structure of an equivalence setting management table in a programming device according to a seventeenth embodiment of the present invention.

[Explanation of symbols]

100 communication network, 200, 200a, 200
b controller device, 201 equivalence means, 202
Local memory, 203 work area, 204 equivalence setting management table, 205 program, 206 program execution means, 207 equivalence and communication error detection means, 300 programming device, 301 data communication means, 302 data file, 303 work area management table, 304 Equivalence setting management table, 3
05 program, 306 programming means, 30
7 data variable name list display means, 308 data variable name list screen, 309 data variable name list display means, 310
Sheet selection / display means, 311 data variable name batch conversion means, 312 data variable name double definition check means,
313 comment-lump conversion means, 314 sheet display switching means, 315 equivalence setting management table comparison means,
316 Equivalence setting management table comparison means, 317 monitor means, 318 Communication abnormal behavior setting means, 400a
-400v communication input / output symbols, 401a-401v
Calculation symbol, 500a to 500v data variable name, 60011 and 60012, comment of data variable name, 700m to 700q controller device identification number,
800p, 800q Sheet identification number.

Claims (18)

[Claims] 1. A network system in which a plurality of controller devices and a programming device are connected by a communication network, wherein the programming device uses a data variable name assigned to a communication input / output symbol when describing communication between the controller devices. On the other hand, a network system is provided with means for automatically allocating a local memory in each controller device, and the controller device is equipped with a device for equalizing the allocated local memories via a network. 2. The programming device, when inputting a data variable name of a communication input / output symbol, displays a list of communication output data variable names already described in another controller device on the communication input side. Also, on the output side of communication, a means for displaying a list of data variable names of communication inputs already described in another controller device and selecting a data variable name from the list is provided. The network system according to claim 1, which is characterized in that. 3. The programming device defines a list of data variable names of communication input / output symbols already input to a program, an input / output type, and a communication input / output symbol to which the data variable name is assigned. The network system according to claim 1 or 2, further comprising: a display unit together with a device identification number of the controller device of the communication destination. 4. The programming device comprises: a list of data variable names of communication input / output symbols that have already been input to the program; and a communication destination in which the communication input / output symbol with the data variable name is defined. 4. The network according to claim 3, further comprising means for displaying, in addition to the device identification number of the controller device, the identification number of the sheet in which the communication input / output symbol with the data variable name is defined. system. 5. The programming device comprises means for selecting an identification number of a sheet in which the communication input / output symbol is defined from the displayed list of data variable names and switching the display to that sheet. The network system according to claim 4, which is characterized in that. 6. The programming device according to claim 1, further comprising means for collectively converting the data variable names of the communication input / output symbols already input to the program. Network system. 7. The programming device comprises means for checking whether or not two or more same data variable names are defined among the data variable names of the communication output symbols already described in the program. The network system according to any one of claims 1 to 6, which is characterized in that. 8. The programming device comprises means for defining a comment in a data variable name of a communication input / output symbol, and means for displaying the comment together with the data variable name for the communication input / output symbol. The network system according to any one of claims 1 to 7. 9. The network system according to claim 8, wherein the programming device comprises means for collectively converting the comments of the data variable names already described in the program. 10. The programming device displays a device identification number of a controller device of a communication destination in which a communication input symbol having the same communication data variable name is defined near or inside the communication output symbol, A means for displaying a device identification number of a controller device of a communication destination in which a communication output symbol having the same communication data variable name is defined is provided near or inside the communication input symbol. The network system according to any one of 1 to 9. 11. The programming device further comprises means for displaying, in addition to the identification symbol of the controller device of the communication destination, the identification number of the sheet in which the symbol of the communication destination is described. The described network system. 12. The network system according to claim 11, wherein the programming device includes means for switching display to a sheet in which the symbol of the communication destination is described. 13. The programming device includes means for detecting whether or not there is a difference from a previously generated equivalence setting management table in accordance with a change in a communication input / output symbol or a data variable name, and displaying the result. The network system according to claim 1, further comprising: a network system. 14. The programming device comprises means for comparing the equivalence setting data in the programming device with the equivalence setting data in each controller device to display whether there is a difference. The network system according to any one of claims 1 to 13, which is characterized. 15. The controller device, when an abnormality occurs in communication, detects the abnormality on the input side of communication,
A means for making the communication status of the input value abnormal when a communication abnormality is detected is provided.
15. The network system according to any one of 14. 16. The programming device reads the communication status for the data in the work area of the controller device, and if the value is abnormal, displays the corresponding communication input symbol by changing the color. The network system according to claim 15. 17. The controller device, when a communication abnormality occurs, determines whether to retain a data value before the communication abnormality according to a preset mode or to change the data value to a preset value. The network system according to claim 15, further comprising means for controlling. 18. The network system according to claim 16, wherein the programming device includes means for presetting behavior at the time of communication abnormality.