JP4656336B2 - PLC network system development support device - Google Patents

Description

  The present invention relates to a development support apparatus for a PLC network system, and more particularly to a development support apparatus for a PLC network system having a function of displaying a network editing screen.

  To construct a control device system, after placing control devices such as programmable controllers (hereinafter referred to as PLCs) on various networks, data such as parameters and programs are transferred to each control device. There is a need (see, for example, Patent Document 1). When transferring data, it is important that data can be accurately transferred to the intended control device, and it is necessary to be able to grasp which control device is set in the system.

  Usually, the development support apparatus is used to create a system configuration diagram of the control device, and data is transferred to each control device based on the created system configuration diagram. At this time, if there are a plurality of networks, data is transferred on the editing screen for each network.

  In the conventional technology, when a PLC spanning a plurality of networks is configured by using a plurality of communication units in the PLC, the PLCs are displayed as separate PLCs on the editing screen of each network. For this reason, it is difficult to grasp the connection between networks, and it takes time to identify which PLC on the actual system is the PLC to which data is to be transferred.

In addition, although data is originally a single PLC, different data is stored for each PLC on each network editing screen, which requires time and effort to manage the data. There is also a risk of transferring unintended data to the PLC.
JP 2005-327237 A

  As described above, in the conventional PLC network system development support device, the same PLC across multiple networks is displayed as a separate PLC on each network editing screen, so that data transfer is attempted. It takes time to identify which PLC on the actual system is a PLC, and because different data is saved for each PLC in each network editing screen, regardless of one PLC. There are problems such as that it takes time and effort to perform management, and there is a risk of transferring unintended data to the PLC.

  The present invention has been made paying attention to the above-mentioned problems, and the object of the present invention is to edit a PLC network prepared for each network on the premise of the existence of a PLC across a plurality of networks. An object of the present invention is to provide a development support apparatus for a PLC network system that makes it easy to grasp the network configuration when observing using a screen.

  The PLC network system development support apparatus according to the present invention comprises a database having a predetermined structure, a node-compatible device search means for handling the database, and a display control means.

  In the database, a network folder and a component folder are provided, and in the network folder, all nodes belonging to the network are registered for each of all existing networks, while in the component folder For every existing device, all the components belonging to that device and the communication interface corresponding to that component are linked and registered, and between all the nodes on the network side and all the communication interfaces on the component side Those with the same entity are registered after being linked.

  The node-compatible device search means refers to the database to acquire a node included in the network for each network based on the association relationship in the network folder, and the communication with the same node and the acquired entity. The interface is acquired from the component folder based on the link relationship between folders, and the device to which the component corresponding to the acquired communication interface belongs is acquired based on the link relationship in the component folder.

  When displaying two or more network edit screens, the display control means refers to a device that is substantially the same as the node acquired by the node corresponding device search means, thereby displaying the device displayed on each network edit screen. It is structured so that the symbol is marked with an indication corresponding to its substance.

  According to such a configuration, the same display (for example, the name of the device) is attached to the device symbols displayed on each network editing screen that have the same actual state. Even when two or more network editing screens are displayed in the display screen, control devices (for example, PLCs) spanning a plurality of networks can be displayed as the same control device on each network editing screen. This makes it easy to grasp the network configuration. In addition, since a plurality of data is not stored in the same control device (such as PLC), the intended data can be accurately transferred to the intended control device on the system.

  A development support apparatus for a PLC network system according to the present invention as seen from another aspect includes a database having a predetermined structure, node number information generation means for handling the database, and display control means. .

  In the database, a network folder and a component folder are provided, and in the network folder, all nodes belonging to the network are registered for each of all existing networks, while in the component folder For every existing device, all the components belonging to that device and the communication interface corresponding to that component are linked and registered, and between all the nodes on the network side and all the communication interfaces on the component side Those with the same entity are registered after being linked.

  The node number information generating means acquires all the components included in the device for each device based on the association relationship in the component folder by referring to the database, and corresponds to each acquired component. A node having the same entity as the communication interface is acquired from the network folder based on the association relationship between the folders, and the number of nodes acquired corresponding to the same device is stored.

  The display control means refers to the number of nodes stored in the node number information generating means when displaying any of the device symbols on the network editing screen. , It is structured so as to attach a specific icon to that effect.

  According to such a configuration, when displaying a PLC network that presupposes the existence of a PLC across a plurality of networks using a separate network editing screen for each network, a specific icon is associated with such a PLC. As a result, it is possible to easily grasp which PLC is a so-called gateway PLC based on a specific icon on the network editing screen.

  The PLC network system development support apparatus according to the present invention as seen from another aspect includes a database having a predetermined structure, relation information generating means for handling the database, and display control means.

  In the database, a network folder and a component folder are provided, and in the network folder, all nodes belonging to the network are registered for each of all existing networks, while in the component folder For every existing device, all the components belonging to that device and the communication interface corresponding to that component are linked and registered, and between all the nodes on the network side and all the communication interfaces on the component side Those with the same entity are registered after being linked.

  When one device is selected via one network editing screen, the relationship information generating means refers to the database, and thereby the communication interface and entity corresponding to each of all components included in the selected device. Acquires the same node from the network folder based on the link relationship between the folders, and further acquires the network to which the acquired node belongs based on the link relationship in the network folder. A communication interface of a component included in one device and a network including nodes having the same entity are stored in association with each other.

  When displaying two or more network editing screens, the display control unit is selected by referring to the relationship between one device stored in the relationship information generating unit and the network related to the one device. Even in a network editing screen corresponding to another network including one device, it is structured so as to give a highlighted display indicating that the device has been selected.

  According to such a configuration, when two or more network editing screens are displayed, if a control device (for example, PLC) across a plurality of networks is selected by a pointing device or the like on any of the network editing screens. In addition, the selected control device symbol is highlighted to indicate that it has been selected, and the device symbol of the control device having the same actual condition is also displayed on a different network editing screen. Is highlighted in the same manner as being selected. Therefore, when two or more networks existing across one gateway PLC are displayed on different network editing screens, the relationship between the gateway PLC and each network can be easily understood.

  According to the development support apparatus for a PLC network system of the present invention, it is possible to easily grasp the network configuration by displaying control devices (for example, PLCs) across a plurality of networks as the same control device on each network editing screen. Become. Also, a plurality of data is not stored in the same control device. As a result, the intended data can be accurately transferred to the intended control device on the system.

  A preferred embodiment of a development support apparatus for a PLC network system according to the present invention will be described below in detail with reference to the accompanying drawings.

  FIG. 1 shows an example of a system configuration diagram showing the relationship between the development support apparatus and the PLC network system according to the present invention. As shown in the figure, this PLC network system includes four PLCs (A) to (D) and one development support apparatus 1. Among them, one PLC (A) is a so-called gateway PLC. That is, the network (N1) including two PLCs (B) and (C) and the network (N2) including one PLC (D) are connected via one PLC (A) functioning as a gateway. Connected. The development support apparatus 1 is connected to the gateway PLC (A).

  The PLC (A) includes a power supply unit a1, a CPU unit a2, an input / output unit a3, a communication unit a4, and a communication unit a5. The PLC (B) includes a power supply unit b1, a CPU unit b2, and a communication unit b3. The PLC (C) includes a power supply unit c1, a CPU unit c2, and a communication unit c3. The PLC (D) further includes a power supply unit d1, a CPU unit d2, and a communication unit d3.

  The general configuration of these power supply unit, CPU unit, input / output unit, communication unit, and the like is well known to those skilled in the art in various documents, and therefore a detailed description thereof is omitted here.

  An example of a hardware configuration diagram of a network-compatible PLC is shown in FIG. As shown in the figure, in such a PLC, the CPU unit U1 and the communication unit U2 are indispensable configurations. The CPU unit U1, which is well known to those skilled in the art, includes a communication interface 11, a microprocessor (MPU) 12, a system memory 13, a data memory 14, a user program memory 15, and an I / O. And a memory 16.

  The communication unit U <b> 2 includes a communication interface 21, a microprocessor (MPU) 22, and a system memory 23.

  The development support apparatus 1 is configured by a personal computer (hereinafter referred to as a personal computer) or the like. In this example, the development support apparatus 1 is configured to be communicable with the CPU unit via the communication interface 11 in the CPU unit U1. The CPU unit U1 and the communication unit U2 are connected via an internal system bus. Furthermore, the communication unit U2 in the PLC is connected to the communication interface of another PLC communication unit having the same configuration. An example of the hardware configuration of the development support apparatus 1 is shown in FIG. In FIG. 1, the development support apparatus 1 includes a CPU 1301, a memory 1302, a hard disk 1303, and a communication I / F 1304 as internal devices. These internal devices are connected to a bus 1305 and send and receive necessary data via the bus 1305.

  The CPU 1301 is a microprocessor that executes an operating system program and application programs installed in the hard disk 1303 in advance. The memory 1302 is a temporary storage unit such as a RAM, and is used as a main memory when the CPU 1301 performs an operation. The hard disk 1303 stores operating system programs and application programs. This application program includes a program for operating a personal computer as a development support apparatus. The hard disk 1303 stores a database to be described later. The communication I / F 1304 is an interface for connecting to the PLC. The development support apparatus 1 transmits / receives data to / from the CPU unit constituting the PLC via the communication I / F 1304. The development support apparatus 1 includes input devices such as a keyboard 1306 and a pointing device 1307 and a display 1308 as external devices. The pointing device 1307 may be configured with a mouse, for example.

  Next, a system diagram showing the structure of a database incorporated in the development support apparatus 1 is shown in FIG. In the figure, a project (denoted as “Project”) indicates a root folder of the project. A component folder (denoted as ComponentFolder) is a folder for storing a control device (Equipment) registered in the project. The control device (denoted as Equipment) stores a plurality of components. Here, the component (denoted as Component) means one unit (for example, a CPU unit, a communication unit, etc.) constituting the PLC if the control device (Equipment) is a PLC. In this component, a plurality of communication interfaces (referred to as CommIF) are stored. Here, the communication interface (CommIF) means a communication interface included in a component. As will be described later, this communication interface (CommIF) is linked (linked) to a node (denoted as Node). The network folder (denoted as NetworkFolder) is a folder for storing networks registered in the project. The network (denoted as Network) is a network registered in the project. A plurality of nodes are stored in this network. A node (denoted as Node) means a node on the network. A node in an actual PLC network system is a device connected to the network, and corresponds to PLC (A) to PLC (D) in the example of FIG. As an important point, the node (Node) and the communication interface (CommIF) are linked (linked).

  That is, as shown in FIG. 3, the structure of this database has a two-system hierarchical structure consisting of a network side and a component side. First, the hierarchical structure on the network side will be described. A network folder (11) is linked under the project (1). Under the network folder (11), the network (111) and the network (112) are linked. Further, a node (1111) and a node (1112) are linked under the network (111). Similarly, the node (1121) and the node (1122) are linked under the network (112). Thus, on the network side, a hierarchical structure having a project hierarchy, a network folder hierarchy, a network hierarchy, and a node hierarchy in order is constructed.

  On the other hand, on the component side, the component folder (12) is linked under the project (1). Under the component folder (12), a control device (121) and a control device (122) are linked. In addition, a component (1211), a component (1212), and a component (1213) are linked under the control device (121). Further, a communication interface (1211a) is linked under the component (1211), a communication interface (1212a) is linked under the component (1212), and a communication interface (1213a) is linked under the component (1213). It is done. Similarly, the component (1221) and the component (1222) are linked under the control device (122). A communication interface (1221a) and a communication interface (1221b) are linked under the component (1221). A communication interface (1222a) is linked under the component (1222).

  Thus, on the component side, a hierarchical structure including a project hierarchy, a component folder hierarchy, a control device hierarchy, a component hierarchy, and a communication interface hierarchy is constructed.

  As important for the present invention, the hierarchical structure on the network side and the hierarchical structure on the component side are linked to each other in the lowest layer. Specifically, in this example, the node (1112) and the communication interface (1213a) are associated with each other, and the node (1122) and the communication interface (1212a) are associated with each other.

  Thus, according to this database structure, each hierarchical structure on the network side and the component side can be arbitrarily searched from the upper side to the lower side or from the lower side to the upper side using the respective linking relationships. It is also possible to trace both hierarchical structures using the tying relationship that connects.

  Next, FIG. 4 shows a flowchart showing an operation procedure for registering a PLC across a plurality of networks in a database. The operation procedure shown in this flowchart is executed in a state where a network editing screen is displayed on the screen of a personal computer constituting the development support apparatus. In the example of FIG. 4, it is assumed that a certain network and a PLC that is a control device on the network are registered on the database, and other networks are not yet registered.

  That is, first, a PLC that is a control device on the network is selected (step 401). Subsequently, an “add to network” menu is selected from the menus prepared in advance (step 402). Subsequently, in a state where the “add to network” menu is selected, a network and a node are respectively added to the hierarchical structure on the network side (steps 403 and 404). Subsequently, in the hierarchical structure on the component side, a control device (Equipment), a component (Component), and a communication interface (CommIF) are respectively added (Steps 405 and 406). Finally, the communication interface and the node are linked (linked) (step 407). The database shown in FIG. 3 is constructed by the above operation.

  Next, FIG. 5 shows a flowchart showing a PLC display procedure across a plurality of networks on the premise of the database shown in FIG.

  In the figure, when processing is started, first, in step 501, an attempt is made to acquire a network registered in a network folder. In the subsequent step 502, it is determined whether or not the network has been acquired. If the network cannot be acquired, the process is immediately terminated. If the network has been acquired, the process proceeds to step 503.

  In step 503, an attempt is made to acquire a node registered in the network. In the subsequent step 504, it is determined whether or not the node has been acquired. If the node cannot be acquired, the process proceeds to step 505 to search for the next network. Proceed to 506.

  In step 506, an attempt is made to acquire a control device by following the link from the node (node-compatible device search means of the first invention). Specifically, the link is traced from the node to reach the communication interface of the lowest layer in the component side hierarchy, and then it is tried whether or not the control device can be reached via the component. In the subsequent step 507, it is determined whether or not the control device has been acquired. If the control device cannot be acquired, the process proceeds to step 508 to search for the next node. Proceed to 509. In step 509, the PLC is displayed on the network editing screen (display control means of the first invention). At this time, the name of the control device acquired in step 506 is used as the PLC name display.

  FIG. 9 shows an explanatory diagram (part 1) of the display screen corresponding to the flowchart of FIG. As shown in the figure, a first network editing screen 300A located in the upper half and a second network editing screen 300B located in the lower half are displayed on the screen of the display device constituting the personal computer. Is done.

  A network system diagram is displayed on each of these network editing screens 300A and 300B by a known method. This network system diagram includes a plurality of display elements. These display elements will be described. 301 is a communication line constituting the network, 302 is a node number display, 303 is a model display, 304 is a model icon display, 305 is a device name display, 306 is a gateway icon, and 307 is a network name. Display 308 is a network number display. Here, the gateway icon indicates that the device to which the gateway icon is attached is a control device across a plurality of networks. As a specific example, a figure, a character, or a combination of a figure and a character may be used.

  In this example, as is clear from the network name 307 and the network number 308, the two network editing screens 300A and 300B display network system diagrams corresponding to different networks. However, as is clear from the device name display 305, the same device name display ("C1" in this example) is displayed on both screens. From this, it can be understood that the two PLCs with the device name display “C1” are the same PLC, although the networks are different. That is, the screens 300A and 300B include four device name displays (“C1”, “C2”, and “C3”) as a whole, and among them, “C1” is displayed on both screens. It is duplicated. From this, the user can surely understand that the PLCs with “C1” are the same.

  Next, FIG. 6 shows a flowchart showing an icon display procedure. When the process is started in the figure, first, in step 601, an attempt is made to acquire a control device stored in the component folder. In the subsequent step 602, it is determined whether or not the control device can be acquired. If the control device cannot be acquired, the process ends immediately, whereas if it can be acquired, the process proceeds to step 603.

  In step 603, an attempt is made to acquire a component stored in the control device. In the subsequent step 604, it is determined whether or not the component has been acquired. If the component cannot be acquired, the process proceeds to step 605 to search for the next control device. Proceed to step 606.

  In step 606, network acquisition is attempted by following the link from the component. Specifically, the link is traced from the component via the communication interface to reach the lowest layer node of the network side hierarchy, and whether or not the network can be reached via the node is tried. . In the subsequent step 607, it is determined whether or not the network can be acquired. If the network cannot be acquired, the process proceeds to step 608 to search for the next component. Proceed to 609.

  In step 609, the number of linked networks is incremented. In the subsequent step 610, whether or not the network is linked is determined based on the number of networks incremented in step 609. The number of nodes acquired corresponding to the same device is stored (node number information generating means of the second invention). In the subsequent step 611, it is determined whether or not there are a plurality of links. If the link is not linked to a plurality of networks, the process proceeds to step 608 to search for the next component. If it is linked to the network, go to step 612.

  Next, in step 612, after the gateway icon is displayed on the PLC on the network editing screen (display control means of the second invention), the process proceeds to step 613. In the subsequent step 613, after the number of linked networks is reset, the process proceeds to step 605, and the process proceeds to search for the next control device.

  FIG. 9 shows an explanatory diagram (No. 1) of the display screen as a result of the process shown in FIG. The details of the display elements 301 to 308 are as described above.

  As apparent from the figure, a gateway icon 306 is attached to each PLC symbol to which “C1” is attached as the device name display. Accordingly, even when only one editing screen is displayed without displaying the two editing screens 300A and 300B in this way, the control device to which the gateway icon 306 is attached due to the presence of the gateway icon 306. The user can understand that (in this example, the PLC) functions as a gateway to another network. Of course, if such a gateway icon 306 is attached in the state where the two screens 300A and 300B are displayed as shown in the figure, this can be understood more clearly.

  Next, when the PLC selected on the network editing screen is a gateway PLC, a process for highlighting the same PLC existing on another window screen will be described. FIG. 7 shows a flowchart showing a cursor display procedure when cursor display is used as an example of highlight display. When the process is started in the figure, first, in step 701, a process of selecting a PLC on the network editing screen is executed via a user's mouse operation and a click operation for selection.

  In the subsequent step 702, an attempt is made to acquire a component stored in a PLC (control device). In the subsequent step 703, it is determined whether or not the component has been acquired. If the component cannot be acquired, the process ends immediately, whereas if it has been acquired, the process proceeds to step 704.

  In step 704, an attempt is made to acquire a network by following links from components. Specifically, the link is traced from the component via the communication interface to reach the lowest layer node of the network side hierarchy, and whether or not the network can be reached via the node is tried. . In the subsequent step 705, it is determined whether or not the network has been acquired (relation information generation means of the third invention). If it cannot be acquired, the process proceeds to step 706 to search for the next component. On the other hand, if it can be obtained, the selected one device, the communication interface of the component included in the one device, and the network including the nodes having the same entity are stored in association with each other, and the process goes to step 707. Proceed with. Next, in step 707, a process of attaching a cursor to the acquired PLC (control device) on the network is executed (display control means of the third invention).

  Here, FIG. 10 shows an explanatory diagram (part 2) of the display screen as a result of executing the flowchart shown in FIG.

  As shown in the figure, even in this example, two network editing screens 300A and 300B are displayed. If any PLC is selected by a mouse click operation or the like in the screen 300B by a known technique, the selected PLC (in this example, the name display “C1”) is selected. A cursor 309a indicating that this has occurred is attached. As is apparent from the figure, the cursor 309a is composed of eight dots positioned at the vertices on the square and in the middle of the four sides.

  Then, the PLC (PLC name “C1”) having the substantially same content is highlighted in the screen 300A. In this example, a cursor display 309b indicating that the selection is the same as in the screen 300B is added. The cursor display 309b is also composed of 8 dots.

  Therefore, according to this cursor display, for example, when there are two or more gateway PLCs between the two screens 300A and 300B, if one of them is selected, the cursor display 309a is attached to that screen. In addition, the same cursor display 309b is added to the other screen, so that the user can easily understand the same device on different network screens.

  In addition, as shown in the example of FIG. 10, when the gateway PLC is selected on one screen 300B, another window screen 300C is displayed on the screen of the display device, and this window screen 300C is selected. Since the network correlation diagram 310 showing the relationship between the PLC that has been connected and all the networks connected thereto is displayed, the user can easily understand the configuration of the entire network by relying on the network correlation diagram 310.

  An explanatory diagram of the other window screen 300C is shown in FIG. As shown in the figure, the network correlation diagram 310 displayed on the window screen 300C includes a network line display 301, a node number display 302, a model display 303, a device name display 305, and a network number display 308. Consists of including.

  Finally, the development support device is connected to the PLC that constitutes the actual PLC network system, and the data (such as a list of communication units and routing tables described later) included in the actual PLC is uploaded to the development support device to create a database. An example in the case of automatically generating will be described. As an example of the automatic generation of this database, a flowchart of the PLC automatic creation processing across a plurality of networks at the time of upload is shown in FIG.

  In the example shown in FIG. 4 earlier, a database corresponding to a PLC spanning a plurality of networks was constructed by a user's manual input operation. However, in the example shown in FIG. 8, when uploading from any PLC real machine, a database related to such PLC can be automatically constructed.

  In the figure, when processing is started, first, in step 801, online connection is made to the PLC. In the subsequent step 802, a list of communication units that can be uploaded is acquired. Here, the communication unit list stores a communication unit type, a network number, a node number, and a unit number as a pair, as shown in FIG. Here, the “network number” is a number for uniquely identifying a plurality of existing networks. The “node number” is a number for uniquely identifying the node in a certain network. The “unit number” is a number for uniquely identifying a plurality of units constituting a certain node.

  In the subsequent step 803, a communication unit is selected from the communication unit list (see FIG. 12A) and uploading is executed. In the subsequent step 804, a routing table is acquired from the actual machine. Here, as shown in FIG. 12B, the routing table is a communication unit and a network number stored as a pair, and indicates a communication path when communicating with another network. .

  In the subsequent step 805, an attempt is made to obtain a network having the same number as the network registered in the routing table (see FIG. 12B) from the database project. In the subsequent step 806, it is determined whether or not acquisition is possible. If acquisition is not possible, the process proceeds to step 809 to create a new control device. On the other hand, if it can be obtained, the process proceeds to step 807.

  In step 807, an attempt is made to acquire a node having the same number as the communication unit from the nodes stored in the acquired network. In the subsequent step 808, it is determined whether or not acquisition is possible. If acquisition is not possible, the process proceeds to step 809 to create a new control device. On the other hand, if it can be obtained, the process proceeds to step 810.

  In step 810, a control device linked to the node is acquired. In the following step 811, a communication unit (component) used for uploading is registered in the control device. In subsequent steps 812 to 815, addition of a communication interface, addition of a network to be uploaded, addition of a node, and link processing between the node and the communication interface are executed.

  By executing such processing, the database having the structure shown in FIG. 3 can be automatically performed in synchronization with the upload processing from the actual device, and the usability of the apparatus can be greatly improved.

  According to the present invention, by displaying PLCs across multiple networks as the same PLC on the editing screen of each network, it is easy to grasp the network configuration and a plurality of data is stored in the same PLC. The situation can be avoided and the intended data can be accurately transferred to the intended control device on the system.

1 is a system configuration diagram of an entire PLC network system including a development support apparatus of the present invention. It is a hardware block diagram of network corresponding PLC. It is a systematic diagram which shows the structure of the database applied to this invention. It is a flowchart which shows the operation procedure for registering PLC over a some network in a database. It is a flowchart which shows the display procedure of PLC (database) over a some network. It is a flowchart which shows the display procedure of an icon. It is a flowchart which shows the display procedure of a cursor. It is a flowchart of the automatic creation process of PLC (database) over a plurality of networks at the time of upload. It is explanatory drawing (the 1) of a display screen. It is explanatory drawing (the 2) of a display screen. It is explanatory drawing (the 3) of a display screen. It is a figure which shows the content of a table. It is a hardware block diagram of the development assistance apparatus which concerns on this invention.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Development support apparatus PLC (A)-(D) Programmable controller N1, N2 Network U1 CPU unit U2 Communication unit 11 Communication interface 12 Microprocessor (MPU)
13 System memory 14 Data memory 15 User program memory 16 I / O memory 21 Communication interface 22 Microprocessor (MPU)
23 System memory (1) to (1222a) Database components 301 Communication line display 302 Node number display 303 Device type display 304 Type corresponding icon 305 Device name display 306 Gateway icon 307 Network name display 308 Network number display 300A, 300B Network editing Screens 309a and 309b Cursor display indicating selection 310 Network correlation diagram

Claims (3)

A network folder and a component folder are provided, and all nodes belonging to the network are linked and registered for each of the networks existing in the network folder, while each device existing in the component folder is registered. All the components belonging to the device and the communication interface corresponding to the component are linked and registered, and the same entity exists between all nodes on the network side and all communication interfaces on the component side. About the database that was linked and registered,
By referring to the database, for each network, the nodes included in the network are acquired based on the link relationship in the network folder, and the communication interface having the same entity as the acquired node is linked between the folders. A node-compatible device search means for acquiring from a component folder based on the relationship, and further acquiring a device to which a component corresponding to the acquired communication interface belongs based on the association relationship in the component folder;
When two or more network editing screens are displayed, by referring to a device that is substantially the same as the node acquired by the node-compatible device search means, the device symbol displayed on each network editing screen is assigned to the entity. A development support apparatus for a PLC network system, comprising: a display control means configured to attach a corresponding display. A network folder and a component folder are provided, and all nodes belonging to the network are linked and registered for each of the networks existing in the network folder, while each device existing in the component folder is registered. All the components belonging to the device and the communication interface corresponding to the component are linked and registered, and the same entity exists between all nodes on the network side and all communication interfaces on the component side. About the database that was linked and registered,
By referring to the database, all the components included in each device are acquired based on the linking relationship in the component folder for each device, and the same entity as the communication interface corresponding to each acquired component is obtained. Node number information generating means for acquiring a node from a network folder based on a linking relationship between folders and storing the number of nodes acquired corresponding to the same device;
When displaying any device symbol on the network editing screen, by referring to the number of nodes stored in the node number information generating means, this is indicated for devices existing across multiple networks. A development support apparatus for a PLC network system, comprising: a display control unit configured to attach a specific icon. A network folder and a component folder are provided, and all nodes belonging to the network are linked and registered for each of the networks existing in the network folder, while each device existing in the component folder is registered. All the components belonging to the device and the communication interface corresponding to the component are linked and registered, and the same entity exists between all nodes on the network side and all communication interfaces on the component side. About the database that was linked and registered,
When one device is selected via one network editing screen, by referring to the database, a node having the same entity as the communication interface corresponding to each of all the components included in the selected device is foldered. Acquired from the network folder based on the linking relationship between them, and further acquires the network to which the acquired node belongs based on the linking relationship in the network folder, and is included in the selected one device and the one device Relationship information generating means for storing and storing a communication interface of a component and a network including nodes having the same entity;
When two or more network editing screens are displayed, the selected one device is included by referring to the relationship between the one device stored in the relationship information generating means and the network related to the one device. A PLC network system development support apparatus, comprising: a display control unit configured to display a highlight indicating that the device has been selected on a network editing screen corresponding to another network. .

Images