Patent Description:
In factory automation (FA), manufacturing equipment provided in a factory is controlled by an industrial network system configured from nodes such as various slave devices controlling and collecting data of the manufacturing equipment, a master device collectively managing the slave devices, etc..

Most issues in the manufacturing equipment of the factory, such as a production line, relate to network communication. When an issue relating to network communication arises, issues relating to the applications of motion control and safety control, etc., operated at the same time in the system occur together.

As a means for solving the communication issue of such network, a ring topology connecting the slave devices is set to ensure network redundancy. However, in order to configure the ring topology, it is necessary to wire communication cables to be ring-like, and required wiring locations are increased. As a result, the issue that the wiring becomes complicated and difficult to understand may arise.

Examples of the technologies for assisting in the network design of various connection configurations including a ring topology include the technology disclosed in Patent Document <NUM>, for example. In Patent Document <NUM>, a technology for designing a system configuration of a control system configured from machines such as a programmable logic controller (PLC), etc. is disclosed.

Patent literature <CIT> relates to a network management device that manages a network including a master device and a slave device connected to the master device, and includes a network configuration diagram display unit that displays a network configuration diagram based on design information of a network according to a design created by a user, a state information acquisition unit that acquires state information relating to a state of the slave device, and a state display unit that displays the state on the network configuration diagram in association with the slave device based on the state information.

Patent literature <CIT> relates to a design assistance device includes: a design information storage section configured to store design information containing at least information of the slave devices and information of a topology in a network system in accordance with a design created by a user; an actual configuration information generation section configured to, based on information collected by the master device from the slave devices in an actual network system, generate actual configuration information containing at least the information of the slave devices and the information of the topology in the actual network system; a comparison section configured to compare the design information and the actual configuration information; and an output section configured to, based on results of comparison by the comparison section, generate a comparison screen indicating the respective configurations of the designed network system and the actual network system along with their commonalities and differences and outputting the comparison screen to a display device.

Patent literature <CIT> relates to a technique for detecting a connection abnormality of a slave device, in a network system including a master device and slave devices. In the network system, data is transmitted from the master device and then is returned to the master device through the respective slave devices. Each slave device has an upstream-side port and a downstream-side port. The connection abnormality detection method includes a step of acquiring topology information of the network system, a step of closing or opening the port of each slave device such that a serial topology is formed to include a target slave device located on the downmost stream side, a step of transmitting inspection data after the control of the port, and a step of detecting a connection abnormality of the device on the basis of a status of return of the inspection data.

In the technology for assisting in the design of a network configuration, by properly connecting wires on the editor for carrying out the design, a connection mode among the slave devices can be expressed in a ring topology in the designed network configuration. However, in order to correctly configure the ring topology on the editor, like in the actual device, it is necessary to connect the wiring of the communication cable, which is complicated and difficult to understand, in the correct ring shape on the editor. At the time of configuring the ring topology on the editor at the design stage and wiring the actual slave devices, there is also a case where an erroneous wire connection on the editor at the design stage is not noticed, and the redundant wiring for the actual slave devices cannot be set correctly.

An objective of the invention is to provide a management device assisting in setting of a ring topology in a designed network configuration.

The following disclosure serves a better understanding of the present invention. A management device according to the invention manages a network including a master device and multiple slave devices connected to the master device. The management device includes: a ring topology assessment unit, assessing whether a ring topology configured from the slave devices is able to be generated based on designed network configuration information created by a user and slave information representing unique information per type of each of the slave devices.

In the management device, the slave information includes port information of each of the slave devices, and each of the port information includes information of a ring start port and a ring end port supporting the ring topology. The ring topology assessment unit prompts the user with the information of the ring start port and the ring end port with which the ring topology is to be generated. The ring topology assessment unit assesses whether the ring topology is able to be generated based on whether the ring end port with which the ring topology is to be generated is an empty port.

In the case the ring topology assessment unit assesses that the ring topology is able to be generated, the ring topology assessment unit configures the ring topology according to a confirmation instruction from the user.

In addition, in the management device, the ring topology assessment unit may identifiably express positions of a plurality of nodes from which the ring topology is configured in a network configuration diagram expressed based on the configuration information.

In addition, in the management device, the ring topology assessment unit may assess, based on whether there is ring topology support in a profile information included in the slave information or the information of the ring start port/ring end port supporting the ring topology of the port information included in the slave information, whether the ring topology is supported for each of the slave devices from which the ring topology is configured.

In addition, in the management device, the ring topology assessment unit may identifiably express the slave device not supporting the ring topology in a network configuration diagram expressed based on the configuration information.

A management method according to the invention manages a network including a master device and multiple slave devices connected to the master device. The management method includes: a ring topology assessment step, assessing whether a ring topology configured from the slave devices is able to be generated based on designed network configuration information created by a user and slave information representing unique information per type of each of the slave devices. The slave information includes port information of each of the slave devices, and each of the port information includes information of a ring start port and a ring end port supporting the ring topology. The ring topology assessment step prompts the user with the information of the ring start port and the ring end port with which the ring topology is to be generated. The ring topology assessment step assesses whether the ring topology is able to be generated based on whether the ring end port with which the ring topology is to be generated is an empty port, and configures the ring topology according to a confirmation instruction from the user in the case the ring topology is assessed being able to be generated.

In addition, a management causing a computer to function as the management device, the management program being provided to cause the computer to function as the ring topology assessment unit, and a computer-readable recording medium storing the management program also fall within the technical scope of the invention.

According to the invention, a management device assisting in setting of a ring topology in a designed network configuration is provided.

Hereinafter, several embodiments of the invention will be described in detail with reference to the accompanying drawings. Although a management device in a network system compliant with the standard of Ethernet for Control Automation Technology (EtherCAT, registered trademark) is described in the following embodiment, the invention is not limited thereto. The invention is applicable to a network system including one or more nodes.

<FIG> is a block diagram illustrating a schematic configuration of an industrial network system <NUM> according to an embodiment of the invention. The industrial network system <NUM> includes a network including a master device <NUM> and slave devices <NUM> connected to the master device <NUM> and a management device <NUM> connected to the master device <NUM>. The master device <NUM> and the slave device <NUM> are connected by a cable <NUM> suitable for EtherCAT communication, and the slave devices <NUM> are also connected to each other by the cables <NUM> suitable for EtherCAT communication. The master device <NUM> and the management device <NUM> are connected through Ethernet (registered trademark) communication or USB communication in a wired or wireless manner. In the embodiment exemplified herein, the case where the nodes connected to the master device <NUM> are all slave devices <NUM> is described.

The master device <NUM> is configured by a device collectively managing the slave devices <NUM>, such as a programmable logic controller (PLC). The master device <NUM> controls the slave device <NUM> by transmitting control commands for performing sequence control to the slave devices <NUM>, and monitors the states of the slave devices <NUM> by receiving various data from the slave devices <NUM>.

The slave devices <NUM> are devices controlling and collecting data of manufacturing equipment and performing control operations on the manufacturing equipment in accordance with the control commands from the master device <NUM> and processes of rewriting and returning the received control commands. As the slave device <NUM>, a slave terminal, an NX unit, a CJ unit, an IO-LInk device, a power unit, a motor unit, a counter unit, an image unit, a communication unit, an I/O unit, etc., are included. The slave device <NUM> is properly connected to the manufacturing equipment in a wired or wireless manner. As the manufacturing equipment, an input device such as a press button, a limit switch, and an output device such as a lamp are included.

The number of the slave devices <NUM> connectible to the master device <NUM> and the topology are not particularly limited. In the embodiment, at most <NUM> slave devices <NUM> are connectible to one master device <NUM>, and, in accordance with the convenience of the cooperation and wiring among the slave devices <NUM>, any topology, such as a ring-like topology, a tree-like topology, or a star-like topology is applicable. Also, in addition to the master device <NUM> and the slave devices <NUM>, the nodes may further include a hub device.

<FIG> is a block diagram illustrating a schematic configuration of the management device <NUM> according to an embodiment of the invention. The management device <NUM> is a computer managing the network of the master device <NUM> and the slave devices <NUM>, and, for example, can be configured from a general-purpose personal computer. As the hardware configuration, the management device <NUM> includes, for example, a central processing unit (CPU), a main storage device (memory), an auxiliary storage device (e.g., hard disk, SSD), a display device, and an input device (e.g., keyboard, mouse).

In addition, as functional blocks, the management device <NUM> includes a communication unit <NUM>, a design assistance control unit <NUM>, a network management unit <NUM>, a network management storage unit (not shown) and an auxiliary storage unit <NUM>. The communication unit <NUM>, the design assistance control unit <NUM>, and the network management unit <NUM> are realized by reading a management program (not shown) stored in the auxiliary storage device to the main storage device and executing the program by the CPU. The management program may be recorded in a non-temporary computer readable recording medium such as a CD-ROM, or the recording medium may also be read by the management device <NUM> to install the management program in the management device <NUM>. Alternatively, the codes of the management program may also be downloaded to the management device <NUM> via a communication network such as the Internet.

The storage unit can be set in the main storage device. In addition, the auxiliary storage device <NUM> can be set in the auxiliary storage device.

The communication unit <NUM> is a communication unit with which the management device <NUM> communicates with the master device <NUM>. For example, the communication unit <NUM> is provided with a function of switching the communication protocol in accordance with the master device <NUM>, a function of regularly transmitting/receiving related data, such as event logs, etc., for regularly monitoring an anomaly occurring in a node, and a function of performing a transmitting/receiving process for acquiring the event logs from each node.

The design assistance control unit <NUM> is provided with a function for controlling the operation of the management device <NUM> between the network including the master device <NUM> and the slave devices <NUM> and the user using the management device <NUM>.

The network management unit <NUM> has a function of assisting in the state management of the network by the user. In order to realize such function, the network management unit <NUM> includes a network configuration diagram expression unit <NUM> and a ring topology assessment unit <NUM>.

In the embodiment, the auxiliary storage unit <NUM> of the management device <NUM> stores in advance a network configuration information D1, as a project file, describing the designed network configuration created by the user, and a slave information D2 describing the unique information per type of each of the slave devices <NUM> from which the industrial network system <NUM> is configured.

The network configuration information D1 describes the profile information of the respective slave devices <NUM> from which the network system <NUM> is configured, the slave connection information, the address information, etc.. The profile information is the information for identifying the type of the slave device <NUM>, and includes, for example, the product code (model), the vendor ID, the revision number, etc., of the slave device. The slave connection information is the information for understanding the connection configuration (topology) of the slave devices. For example, the slave connection information includes the information for specifying the devices and the ports of the connection destinations of the slave devices, the connection information between ports, the information relating to the state of the ring topology, etc. The address information is the information indicating the values of the node addresses assigned to the slave devices.

The slave information D2 is a file created in advance in the format such as the XML format, etc., by the vendor of each slave device <NUM>. The slave information D2 includes profile information and port information. The profile information is the information for identifying the types of the slave devices <NUM>, and includes, for example, the product codes (models), the vendor IDs, the revision numbers, and whether there is ring topology support, etc., of the slave devices. The port information is the information relating to the ports owned by the slave devices <NUM>, and includes, for example, information such as the number of ports, the types of ports, the start port/end port supporting the ring topology, etc. Since the slave information D2 is the file created by the vendor of each slave device <NUM>, the information on whether there is support for ring topology, and the start port/end port for supporting the ring topology is the unique information of each slave device (i.e., the specification of each slave device).

The network configuration diagram expression unit <NUM> is a functional block expressing the network configuration diagram showing the connection relationship of the nodes. The network configuration diagram expression unit <NUM> refers to the network configuration information D1 stored in the auxiliary storage unit <NUM> and graphically expresses a network configuration diagram <NUM> shown in <FIG>. In the network configuration diagram <NUM>, the nodes included in the network are indicated as icons and are expressed as a tree by connection lines <NUM> and <NUM>. In addition, in the vicinity of each icon, the node address and the type name of the node are expressed. It should be noted that the specific expression mode of the network configuration diagram <NUM> is not limited thereto, as long as the user can intuitively understand the network configuration.

The ring topology assessment unit <NUM> is a functional block having a function of assessing whether a ring topology configured from the slave devices <NUM> can be generated for the industrial network system represented by the network configuration information D1 and a function for assessing whether the ring topology is supported for each slave device from which the ring topology is configured. The ring topology assessment unit <NUM> assesses whether the ring topology configured from the slave devices <NUM> can be generated based on the designed network configuration information D1 created by the user and the slave information D2 representing the unique information per type of each of the slave devices <NUM>, performs an assessment on whether the ring topology is supported based on the slave information D2.

In the following, the function of the ring topology assessment unit <NUM> is described in detail. Firstly, terms relating to ring topology as used in the following descriptions are described with reference to <FIG>. Then, with reference to <FIG>, the above functions provided in the ring topology assessment unit <NUM> are described in greater detail.

<FIG> is a schematic diagram for describing the names of the slave devices and the ports in the ring topology.

As an example, five slave devices <NUM> (2a to 2e) are shown in <FIG>. In the example as shown, three slave devices 2a to 2c of the slave devices are connected in a ring shape. The mode in which the slave devices 2a to 2c are connected in a ring shape is referred to as a ring topology, and the cables <NUM> (4a) connecting the slave devices 2a to 2c in a ring shape are referred to as main lines of the ring topology. The remaining two slave devices 2d and 2e are connected in series from the slave device 2b from which the ring topology is configured. The cables <NUM> (4b) connecting the slave device 2b from which the ring topology is configured and the slave devices 2d and 2e are referred to as branch lines of the ring topology.

In the example as shown, the slave device 2a is referred to as the start slave of the ring topology, and the slave device 2c is referred to as the terminal slave of the ring topology. In addition, in the connection relationship among the ports as shown, a port X2 of the slave device 2a is referred to as the start port of the ring topology, and a port X3 of the slave device 2a is referred to as the end port of the ring topology. The terminal port of the slave device refers to the port whose topology circulation order is the last among the respective ports provided in the slave devices <NUM>.

<FIG> are diagrams illustrating examples expressing a series of screens at the time of setting the ring topology on the editor.

Referring to <FIG> and <FIG>, in the network configuration diagram <NUM>, the nodes included in the network are indicated by icons and are expressed as a tree by the connection lines <NUM>. In the network configuration diagram <NUM>, the user may select the slave device (node) to be set as the start of the ring topology, and notifies the ring topology assessment unit <NUM> that a ring topology is to be configured by using the selected slave device as the start through a context menu <NUM>. In the example as shown, the node with a node address E001 is selected, and the ring topology assessment unit <NUM> assesses whether a ring topology can be generated by using the node with the node address E001 as the start.

The ring topology assessment unit <NUM> acquires profile information such as the product code (model), the vendor ID, the revision number, etc., of the selected slave device from the network configuration information D1.

Then, based on the profile information of the selected slave device, the ring topology assessment unit <NUM> acquires port information including information of start port/end port supporting the ring topology, which relates to the selected slave device, from the slave information D2. In the case where the information of the start port cannot be acquired, the ring topology assessment unit <NUM> assesses that the selected slave device cannot be set as the start of the ring topology, and express ineffectiveness in a context menu <NUM>.

Then, the ring topology assessment unit <NUM> assesses whether the end port of the ring topology is an empty port based on the connection information among the ports in the slave connection information included in the network configuration information D1. In the example as shown, for the port X3 with the node address E001, whether the port X3 is an empty port is assessed. In the case where the end port of the ring topology is not an empty port, the ring topology assessment unit <NUM> expresses ineffectiveness in the context menu <NUM>. Specifically, at the time of assessing whether the end port of the ring topology is an empty port, for the ports between the slave devices <NUM>, the ring topology assessment unit <NUM> traces the connection relationship between the input port and the output port in the order from the input port to the output port by using the selected slave device as the start.

Referring to <FIG>, the ring topology assessment unit <NUM> uses the information of the start port/end port supporting the ring topology, which is acquired in relation to the selected slave device, and expresses a confirmation dialogue <NUM>. The confirmation dialogue <NUM> expresses the information of start port/end port in which the cable redundancy by the ring topology is to be enabled and a confirmation message. In the example as shown, the port X2 with the node address E001 is set as the start port, and the port X3 is set as the end port.

Through the expression of the confirmation dialogue <NUM>, the ring topology assessment unit <NUM> performs a confirmation with the user on enabling cable redundancy (whether the ring topology can be generated). In addition, with the port name of the branch slave being expressed in the confirmation dialogue <NUM>, an erroneous setting by the user is prevented. In addition, by expressing the influence resulting from enabling cable redundancy as a confirmation message in the confirmation dialogue <NUM>, the user is notified in advance of a possibility that an influence may be generated on the control program operating in the respective slave devices <NUM> from which the ring topology is configured.

With the user pressing the "OK" button in the confirmation dialogue <NUM>, the user instructs the ring topology assessment unit <NUM> to enable the cable redundancy. The ring topology assessment unit <NUM> sets the selected slave device as the start, traces the connection relationship between the input port and the output port in the order from the input port to the output port, and configures the ring topology based on the start port/end port information. That is, the ring topology assessment unit <NUM> acquires the terminal port of the slave device connected below the start point through the network configuration information D1, and connects the terminal port of the slave device and the end port of the ring topology to configure the ring topology. After configuring the ring topology, the ring topology assessment unit <NUM> sets the value "effective" to the information relating to the state of the ring topology of the slave device (node) as the start of the ring topology in the network configuration information D1.

In the example shown in <FIG>, the ring topology assessment unit <NUM> configures the ring topology at the node with a node address E003 and a node with a node address E005 from the node with the address E001. In addition, the ring topology assessment unit <NUM> sets the value "effective" to the information relating to the state of the ring topology of the node with the address E001 in the network configuration information D1.

Referring to <FIG>, the ring topology assessment unit <NUM> identifiably expresses the positions of the nodes from which the ring topology is configured in the network configuration diagram <NUM>.

In the example shown in <FIG>, the ring topology assessment unit <NUM> indicates that the ring topology is configured from the node with the node address E003 and the node with the node address E005 from the node with the address E001 by using double lines <NUM> indicating the connection among the respective nodes in the tree expression in the network configuration diagram <NUM> for expression. The double line <NUM> is also used for expression between the output port of the node with the node address E005 and the output port X3 of the node address E001. In addition, in the example shown in <FIG>, in order to illustrate the configuration of the ring topology, the ring topology assessment unit <NUM> expresses expressions <NUM> meaning that the ring topology is configured in the vicinities of the output ports X2 and X3 of the node with the node address E001. Accordingly, regarding the slave devices <NUM> on the editor, from which the ring topology is to be configured, the user can more easily understand the places where redundant wirings are set in the graphical expression in the designed network configuration diagram <NUM>. Therefore, the operation for setting the ring topology in the designed network configuration is simplified.

It is noted that the mode for expressing the ring topology in the network configuration diagram <NUM> is not limited to the above mode. For example, a mode in which the icons and/or the connection lines are expressed with blinking or highlighting can be applied.

Referring to <FIG>, the ring topology assessment unit <NUM> assesses whether the ring topology is supported for each node from which the ring topology is configured on the editor.

Firstly, in order to specify the node where the assessment is performed, the ring topology assessment unit <NUM> acquires the profile information, such as the product code (model), the vendor ID, the revision number, etc., of each slave device from the start slave to the terminal slave of the ring topology from the network configuration information D1. Then, the ring topology assessment unit <NUM> assesses whether there is ring topology support based on the slave information D2 for each slave device from the start slave to the terminal slave of the ring topology in which the type is specified from the acquired profile information.

For example, the ring topology assessment unit <NUM> assesses whether the ring topology is supported based on whether there is ring topology support in the profile information included in the slave information D2. Alternatively, the ring topology assessment unit <NUM> assesses whether the ring topology is supported based on the information of the start port/end port supporting the ring topology of the port information included in the slave information D2.

In the case of assessing that the slave device <NUM> not supporting the ring topology is connected in the ring topology, the ring topology assessment unit <NUM> identifiably expresses the slave device <NUM> not supporting the ring topology in the network configuration diagram <NUM>.

The example shown in <FIG> illustrates a case where the user erroneously or carelessly configure the ring topology by using a node with a node address E007 not supporting the ring topology due to the specification of the device. The user configures the ring topology in the node with the node address E003, the node with the node address E005, and the node with the node address E007 from the node with the node address E001. However, in the example shown in <FIG>, an icon <NUM> is expressed in the vicinity of the node with the node address E007, and that the node with the node address E007 does not support the ring topology is identifiably expressed. In addition, in the example shown in <FIG>, a message <NUM> indicating that a node not supporting the ring topology is connected in the ring topology is further expressed as a tool tip. In the mode shown in <FIG>, an icon <NUM> is a warning icon. Accordingly, among the slave devices on the editor from which the ring topology is configured, the user can more easily notice the slave device not supporting the ring topology through the graphical expression in the designed network configuration diagram <NUM>. Therefore, the operation for setting the ring topology in the designed network configuration is simplified.

It is noted that the mode for expressing the node not supporting the ring topology in the network configuration diagram <NUM> is not limited to the above mode. For example, a mode in which the icons and/or the connection lines are expressed with blinking or highlighting can be applied.

<FIG> is a diagram illustrating an example expressing a screen at the time of canceling the setting of the ring topology on the editor.

In the network configuration diagram <NUM>, the user may select the slave device (node) in which the setting of the ring topology is to be canceled, and notifies the ring topology assessment unit <NUM> that the ring topology configured by using the selected slave device as the start is to be canceled through a context menu <NUM>. In the example as shown, the node with the node address E001 is selected, and the ring topology assessment unit <NUM> cancels the setting of the ring topology configured by using the node with the node address E001 as the start point.

The ring topology assessment unit <NUM> uses the information of the start port/end port supporting the ring topology, which is acquired in relation to the selected slave device, and expresses a confirmation dialogue (not shown). The confirmation dialogue expresses the information of the start port/end port in which the cable redundancy by the ring topology is to be disabled and a confirmation message. With the user pressing the "OK" button in the confirmation dialogue, the user instructs the ring topology assessment unit <NUM> to disable the cable redundancy.

Then, the ring topology assessment unit <NUM> sets the value "ineffective" to the information relating to the state of the ring topology of the slave device as the start of the ring topology in the network configuration information D1. In addition, in the tree expression in the network configuration diagram <NUM>, by using, for expression, the double line <NUM> indicating the connection among the respective nodes from which the ring topology is configured and the connection line <NUM> meaning normal connection, the ring topology assessment unit <NUM> identifiably expresses the cancellation of the setting of the ring topology in the network configuration diagram <NUM>. In addition, in the case where the icon <NUM> or the message <NUM> indicating that a node not supporting the ring topology is connected in the ring topology is expressed, the ring topology assessment unit <NUM> cancels the expressions of the icon <NUM> and the message <NUM>.

<FIG> is a flowchart illustrating a process flow in a management method for managing the network including the master device <NUM> and the slave device <NUM>. The same figure shows the process procedure at the time of setting the ring topology on the editor in the management device <NUM>.

First, when the user starts the management program in the management device <NUM> to open the project file (S1), the network management unit <NUM> is started, and the network configuration diagram expression unit <NUM> reads the network configuration information D1 stored in the auxiliary storage unit <NUM> to the storage unit (not shown) (S2). Then, when the user presses an editor start button (not shown) in the screen of the management program, in the management device <NUM>, the design assistance control unit <NUM> is started (S3). Then, the network configuration diagram expression unit <NUM> expresses the network configuration diagram <NUM> based on the network configuration information D1 (S4).

In the network configuration diagram <NUM>, when the user instructs the management device <NUM> to enable cable redundancy, the ring topology assessment unit <NUM> assesses whether a ring topology can be generated based on the network configuration information D1 and the slave device D2 (S5) and identifiably expresses the positions of the nodes from which the ring topology is configured on the editor in the network configuration diagram <NUM> (S6). Accordingly, regarding the slave devices <NUM> on the editor, from which the ring topology is to be configured, the user can more easily understand the places where redundant wirings are set in the graphical expression in the designed network configuration diagram <NUM>. Therefore, the operation for setting the ring topology in the designed network configuration is simplified.

In addition, the ring topology assessment unit <NUM> performs an assessment relating to whether there is ring topology support based on the slave information D2, and assesses, for each of the nodes from which the ring topology is configured on the editor, whether the ring topology is supported (S7). The ring topology assessment unit <NUM> identifiably expresses the slave device <NUM> not supporting the ring topology in the designed network configuration diagram <NUM> (S8). Accordingly, among the slave devices on the editor from which the ring topology is configured, the user can more easily notice the slave device not supporting the ring topology through the graphical expression in the designed network configuration diagram <NUM>. Therefore, the operation for setting the ring topology in the designed network configuration is simplified.

Claim 1:
A management device (<NUM>), managing a network comprising a master device (<NUM>) and a plurality of slave devices (<NUM>) connected to the master device (<NUM>), the management device (<NUM>) comprising:
a ring topology assessment unit (<NUM>), assessing whether a ring topology configured from the slave devices (<NUM>) is able to be generated based on designed network configuration information (D1) created by a user and slave information representing unique information per type of each of the slave devices (<NUM>),
wherein the slave information comprises port information of each of the slave devices (<NUM>), and each of the port information comprises information of a ring start port (X2) and a ring end port (X3) supporting the ring topology,
wherein the ring topology assessment unit (<NUM>) is adapted to prompt the user with the information of the ring start port (X2) and the ring end port (X3) with which the ring topology is to be generated,
wherein the ring topology assessment unit (<NUM>) is adapted to assess
whether the ring topology is able to be generated based on whether the ring end port (X3) with which the ring topology is to be generated is an empty port,
in the case the ring topology assessment unit (<NUM>) assesses that the ring topology is able to be generated, the ring topology assessment unit (<NUM>) configures the ring topology according to a confirmation instruction from the user.