Patent Description:
Conventionally, in the field of factory automation (FA), a system in which a control device and various devices such as a sensor, an actuator, and the like are network-connected has been used. With the development of information and communication technology (ICT), the application of more advanced communication technology is progressing.

For example, by using a network technology referred to as common industrial protocol (CIP) managed and provided by ODVA, Inc. , which is headquartered in the United States, communication between control devices, and communication between a control device and an arbitrary device can be achieved (see Non-Patent Literature <NUM>).

Non-Patent Literature <NUM>:<NPL>], the Internet <URL: https://www. org/Technology-Standards/Common-Industrial-Protocol-CIP/Overview>.

<NPL>, relates to documents of user manual for POINT Guard I/O Safety Modules. <NPL>, relates to documents of user manual for Controllers.

In order to implement the communication using the advanced communication technology as described above, each control device and/or device connected to the same network is required to be appropriately set. On the other hand, multiple devices may be connected to the same network, and there is a problem that the setting operation is complicated and troublesome.

The following disclosure serves a better understanding of the present invention. The present invention has been made in view of the above problem, and the purpose of the present invention is to provide a support device, a support program, and a setting method capable of easily setting required identification information even when multiple safety devices are connected to the same network.

According to an example of the present invention, the support device is capable of communicating with a control device network-connected to one or a plurality of safety devices. Each of the one or plurality of safety devices holds setting identification information that identifies the setting of the own device. The control device holds, for each of the one or plurality of safety devices, connection setting information set for establishing a connection with the safety device. The one or plurality of safety devices include a target safety device for which a first establishment method has been set, wherein the first establishment method establish a connection with the control device in accordance with a result of a comparison between the connection setting information and the setting identification information. The support device includes a memory part for storing a support program that assists in the setting of the control device, and a processor for executing the support program. The support program includes a first command and a second command. The first command is a command for acquiring the setting identification information from the target safety device. The second command is a command for setting, in the connection setting information corresponding to the target safety device, the setting identification information acquired from the target safety device in response to the execution of the first command.

According to the invention, a user may activate the support program to execute the first command and the second command. Thereby, the setting identification information acquired from the target safety device is automatically set in the connection setting information held by the control device. Therefore, the user can save the trouble of activating a setting tool for the safety device and recording the setting identification information of the safety device on a memo paper or the like. As a result, even when multiple safety devices are connected to the same network, the user can easily set the setting identification information for identifying the setting of each of the multiple safety devices in the control device.

In the above invention, each of the one or plurality of safety devices holds device identification information that identifies the own device. The support program further includes a third command and a fourth command. The third command is a command for acquiring the device identification information from the target safety device. The fourth command is a command for comparing the device identification information acquired from the target safety device in response to the execution of the third command with first setting information held in association with the target safety device. The first command and the second command are executed according to the fact that a comparison result obtained by executing the fourth command shows a match. According to the invention, it is possible to suppress erroneous setting of connection setting information.

In the above invention, each of the one or plurality of safety devices holds attribute information representing the attribute of the own device. The support program further includes a fifth command and a sixth command. The fifth command is a command for acquiring the attribute information from the target safety device. The sixth command is a command for comparing the attribute information acquired from the target safety device in response to the execution of the fifth command with second setting information held in association with the target safety device. The first command and the second command are executed according to the fact that a comparison result obtained by executing the sixth command shows a match. According to the invention, it is possible to suppress erroneous setting of connection setting information.

In the above invention, the support device includes a user interface. The support program further includes a seventh command for setting either the first establishment method or a second establishment method for each of the one or plurality of safety devices according to the input to the user interface, wherein the second establishment method establishes a connection with the control device without using the setting identification information. The target safety device is a safety device for which the first establishment method has been set by executing the seventh command.

According to the invention, the first command is executed only for the safety device in which the setting identification information is required for establishing the connection. Thereby, unnecessary communication can be suppressed in the setting of the control device.

In the above invention, the support device includes a user interface. The support program further includes an eighth command for classifying, according to the input to the user interface, each of the one or plurality of safety devices into either a first group in which the connection setting information is automatically set or a second group in which the connection setting information is manually set. The target safety device is a safety device classified into the first group by executing the eighth command.

According to the invention, the first command is not executed for the safety device in which the connection setting information is manually set for the control device. Thereby, unnecessary communication can be suppressed in the setting of the control device.

According to an example of the present invention, the support program is executed by a computer capable of communicating with a control device network-connected to one or a plurality of safety devices and assists in the setting of the control device. Each of the one or plurality of safety devices holds setting identification information that identifies the setting of the own device. The control device holds, for each of the one or plurality of safety devices, connection setting information set for establishing a connection with the safety device. The one or plurality of safety devices include a target safety device for which a first establishment method has been set, wherein the first establishment method establishes a connection with the control device in accordance with a result of a comparison between the connection setting information and the setting identification information. The support program makes the computer execute a first step and a second step. The first step is a step of acquiring the setting identification information from the target safety device. The second step is a step of setting the setting identification information acquired from the target safety device in the connection setting information corresponding to the target safety device.

According to an example of the present invention, the setting method of a control device in a support device capable of communicating with the control device network-connected to one or a plurality of safety devices includes: a step in which the support device acquires the setting identification information from the target safety device; and a step in which the support device sets the setting identification information acquired from the target safety device in the connection setting information corresponding to the safety device.

According to the present invention, even when multiple safety devices are connected to the same network, the required identification information can be easily set.

Embodiments of the present invention are described in detail with reference to the drawings. Note that, the same or corresponding parts in the drawings are designated by the same reference signs and the descriptions thereof are not repeated.

First, an example of a case in which the present invention is applied is described. <FIG> is a schematic diagram showing a functional configuration example of a safety control system <NUM> according to the embodiment. The safety control system <NUM> according to the embodiment provides an architecture for achieving function safety defined in, for example, IEC <NUM> or the like.

The safety control system <NUM> typically includes a control device <NUM> that achieves safety control related to function safety, and one or a plurality of safety devices network-connected to the control device <NUM>. In the safety control system <NUM> exemplified in <FIG>, the control device <NUM> is connected to three safety devices <NUM>-<NUM>, <NUM>-<NUM>, and <NUM>-<NUM> (hereinafter, also collectively referred to as "safety device <NUM>").

In this specification, "standard control" is typically a general term of processing for controlling a control target in accordance with predetermined requirement specifications. In addition, in this specification, "safety control" is a general term of processing for preventing the safety of a human from being threatened by some equipment, machine, or the like due to some failure. The safety control includes, for example, processing of stopping the control target not only when the behavior of the control target is different from the original behavior but also when it is judged that some abnormality has occurred in the control device <NUM>.

In this specification, "device" includes apparatuses capable of being connected via an arbitrary network. The device includes at least a part of a single sensor, a single actuator, a relay apparatus for connecting one or a plurality of sensors or actuators to a network, and various control devices such as a robot controller, a temperature controller, a flow rate controller, and the like. In particular, the "device" for achieving safety control is also referred to as "safety device".

Identification information such as an IP address, a safety network number (SNN), an originator unique network identifier (OUNID), a target unique network identifier (TUNID), a safety configuration identifier (SCID), and the like are used to establish a connection and exchange messages between the control device <NUM> and the safety device <NUM>.

The IP address is a network address allocated to the control device <NUM> and each safety device <NUM>. The IP address is set so as not to repeat in the same network.

The SNN is an example of network identification information, and is identification information set in a range in which the control device <NUM> is handled as a single network. The SNN is set so as not to mutually repeat in each network in the safety control system <NUM>.

The OUNID is identification information for identifying the control device <NUM>. The TUNID is identification information for identifying each safety device <NUM>. Typically, a data string in which the SNN of a network to which each safety device <NUM> belongs and the IP address of each safety device <NUM> are combined is used as the TUNID. In this way, the TUNID, which is device identification information, may be determined based on the IP address of a target safety device <NUM> and the SNN which is network identification information set for the network to which the target safety device <NUM> belongs.

The SCID is setting identification information that is allocated when required setting is performed on each safety device <NUM> and identifies the setting (configuration) of each safety device <NUM>. The SCID is used as a signature in the setting (safety setting) of each safety device <NUM>. The SCID is a combination of a safety configuration CRC (SCCRC) and a safety configuration time stamp (SCTS). The SCCRC is a cyclic redundancy check (CRC) for detecting errors that may occur in setting data (configuration data) of the safety device <NUM>. The SCTS is data indicating a date on which the setting data of the safety device <NUM> is revised, and identifies the revision.

In CIP Safety, which is a communication protocol compatible with a function safety standard such as IEC <NUM>, "Type <NUM>", "Type 2a", and "Type 2b" are defined as methods for establishing a connection between the control device <NUM> and the safety device <NUM>.

"Type <NUM>" is an establishment method in which a safety device is set when a connection is established. However, high-functional safety devices such as a controller, a robot, and the like usually do not support Type <NUM>. For a high-functional safety device, a tool for setting is provided separately, and the setting is performed in advance using the tool.

"Type 2a" is an establishment method in which a safety device is not set when a connection is established, and the SCID that identifies the setting performed in advance on the safety device is used to check whether the setting of the safety device is correct. When the SCID held by the control device matches the SCID held by the safety device, the connection is established, and when the SCID held by the control device is different from the SCID held by the safety device, the establishment of the connection fails.

"Type 2b" is an establishment method in which a safety device is not set when a connection is established, and the check using the SCID is also not performed. "Type 2b" cannot detect that the setting of the safety device has been revised, and thus there is a risk that the safety function is impaired. Therefore, "Type 2b" is used, for example, at the time of starting up and adjusting a safety control system.

The safety control system <NUM> further includes a support device <NUM> capable of communicating with the control device <NUM>.

The support device <NUM> assists in the settings for the control device <NUM> and the safety device <NUM>. Specifically, a master setting tool <NUM> and slave setting tools <NUM> to <NUM> are preinstalled in the support device <NUM>. The master setting tool <NUM> is a support program that assists in the setting for the control device <NUM>, and is provided by the manufacturer or the seller of the control device <NUM>. The slave setting tools <NUM> to <NUM> are support programs that respectively assist in the settings for the safety devices <NUM>-<NUM> to <NUM>-<NUM>, and are respectively provided by the manufacturer or the seller of the safety devices <NUM>-<NUM> to <NUM>-<NUM>.

A user activates the slave setting tools <NUM> to <NUM> in the support device <NUM> and performs necessary operations to thereby set the safety devices <NUM>-<NUM> to <NUM>-<NUM> respectively. When the setting of each of the safety devices <NUM>-<NUM> to <NUM>-<NUM> is completed, a SCID that identifies the setting is allocated. The SCIDs allocated to the settings of the safety devices <NUM>-<NUM> to <NUM>-<NUM> are respectively stored in memory parts <NUM> of the safety devices <NUM>-<NUM> to <NUM>-<NUM>. Moreover, the SCIDs allocated to the settings of the safety devices <NUM>-<NUM> to <NUM>-<NUM> are respectively confirmed on the slave setting tools <NUM> to <NUM>.

The user activates the master setting tool <NUM> in the support device <NUM> and performs necessary operations to thereby set the control device <NUM>. The master setting tool <NUM> includes a group of commands for setting connection setting information <NUM> in the control device <NUM> in order to establish a connection with the safety device <NUM> according to the user operation.

As described above, when the safety device <NUM> is a high-functional device, either "Type 2a" or "Type 2b" can be selected as the establishment method of a connection. When "Type 2a" is selected, the connection between the control device <NUM> and the safety device <NUM> is established using the SCID that identifies the setting of the safety device <NUM>. Therefore, the connection setting information <NUM> corresponding to the safety device <NUM> for which "Type 2a" is selected includes the SCID that identifies the setting of the safety device <NUM>.

Conventionally, when a connection with the safety device is established according to "Type 2a", the setting according to the following procedures (a) to (c) is performed in advance on the control device.

According to the conventional setting method, the user needs to activate the corresponding slave setting tool and record the SCID for each safety device for which "Type 2a" is selected. Therefore, for the safety device <NUM> to which a connection is established according to "Type 2a", the setting on the control device is troublesome and complicated. In particular, when multiple safety devices are connected to the same network, it is necessary to perform the above procedure (a) for each of the multiple safety devices, which requires a lot of work of the user. In addition, the SCID is updated every time the setting of the safety device is revised. Therefore, it is necessary to perform the above procedures (a) to (c) every time the setting of the safety device is revised.

In the embodiment, in order to reduce this complicated work, the master setting tool <NUM> includes the following command (A) and command (B). The command (A) is a command for acquiring the SCID from the safety device <NUM> to which a connection is established according to "Type 2a". The command (B) is a command for setting the SCID acquired by executing the command (A) in the connection setting information <NUM>. Besides, the master setting tool <NUM> is used to perform the setting according to the following procedures (<NUM>) to (<NUM>) on the control device.

According to the above procedures (<NUM>) to (<NUM>), the user can save the work of activating the slave setting tool and recording the SCID that identifies the setting of the safety device on a memo paper or the like as in the conventional case. As a result, even when multiple safety devices <NUM> are connected to the same network, the user can easily set the SCID that identifies the setting of each of the multiple safety devices <NUM> in the control device <NUM>.

Next, a specific example of the safety control system <NUM> according to the embodiment is described.

A configuration example of the safety control system <NUM> according to the embodiment is described.

<FIG> is a schematic diagram showing the configuration example of the safety control system according to the embodiment.

In <FIG>, the safety control system <NUM> including two control devices 2A and 2B (hereinafter, sometimes collectively referred to as "control device <NUM>") is shown as an example.

The control device <NUM> is capable of standard control for controlling a control target (not shown) and safety control.

Although both the standard control and the safety control may be achieved by the same unit, the control device <NUM> is configured by a standard control unit <NUM> mainly in charge of control for the control target and a safety control unit <NUM> mainly in charge of the safety control. As described later, the standard control is achieved by executing a standard control program in the standard control unit <NUM>, and the safety control is achieved by executing a safety program in the safety control unit <NUM>. One or a plurality of safety IO units <NUM> may be mounted on the control device <NUM>.

The safety IO unit <NUM> is responsible for the input of signals from a safety component and/or the output of signals to a safety component. In this specification, the "safety component" mainly includes an arbitrary apparatus used for the safety control, and includes, for example, a safety relay, various safety sensors, and the like.

The standard control unit <NUM> is communicably connected to the safety control unit <NUM> and the safety IO unit <NUM> via an internal bus. In the control device <NUM> shown in <FIG>, communication ports <NUM> and <NUM> for the connection with another control device <NUM> or another device are arranged in the standard control unit <NUM>, and the safety control unit <NUM> uses the standard control unit <NUM> connected via the internal bus to exchange data with the another control device <NUM> or another device.

The standard control unit <NUM> includes the communication port <NUM> for physical connection with a subordinate network <NUM>, and the communication port <NUM> for physical connection with a superordinate network <NUM>. As an example, safety devices <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>. are connected to the subordinate network <NUM>, and one or a plurality of human machine interfaces (HMI) <NUM> and a server apparatus <NUM> are connected to the superordinate network <NUM>. In addition, the control device 2A and the control device 2B are also connected via the superordinate network <NUM>.

The HMI <NUM> displays state values and the like held by the control device <NUM> and receives the user operation to output the content of the received user operation to the control device <NUM>.

The server apparatus <NUM> includes a database for collecting information from the control device <NUM>, an operation management system for giving various settings such as a recipe to the control device <NUM>, and the like.

In <FIG>, a safety IO device is shown as an example of the safety device <NUM>. The safety IO device is one type of relay apparatus for forming a network for signals exchanged with one or a plurality of safety components (for example, an emergency stop button, a safety switch, a light curtain, and the like). The safety IO device sends out detection signals and the like output from the safety component to the network and outputs instructions transmitted via the network to the target safety component. Moreover, the safety device is not limited to the safety IO device shown in <FIG>, and any apparatus for achieving function safety can be used.

A protocol related to the data transmission of the subordinate network <NUM> and the superordinate network <NUM> may be an industrial network protocol such as EtherNet/IP (registered trademark), DeviceNet (registered trademark), CompoNet (registered trademark), or the like. As described later, a program (application) executed in the standard control unit <NUM> and/or the safety control unit <NUM> employs the protocol related to data transmission to achieve data exchange in accordance with a communication protocol such as a common industrial protocol (CIP), CIP Safety, or the like.

That is, the control device <NUM> may employ an architecture in which an industrial network protocol such as EtherNet/IP (registered trademark), DeviceNet (registered trademark), CompoNet (registered trademark), or the like is combined with a communication protocol (function at an application layer) such as CIP, CIP Safety, or the like.

The description below mainly illustrates the architecture in which the CIP Safety is employed in addition to EtherNet/IP (registered trademark) between the safety control unit <NUM> and one or a plurality of safety devices <NUM>.

Each of the safety devices <NUM> has a memory part <NUM> for storing information required for establishing a connection with the control device <NUM>. The memory part <NUM> holds the IP address, the TUNID, the SCID, attribute information, and the like. The attribute information represents the attributes (model, vendor name, product code, state, serial number, product name, and the like) of the safety device <NUM>. The memory part <NUM> is implemented using a flash memory, a non-volatile RAM (NVRAM), or the like.

The support device <NUM> is communicable with the control device <NUM> via a communication port <NUM>. That is, the support device <NUM> is configured to be capable of communicating with the control device <NUM> that is network-connected to one or a plurality of safety devices <NUM>. The support device <NUM> provides the user with functions such as development, debugging, and the like of the program executed in the control device <NUM> (the standard control unit <NUM> and/or the safety control unit <NUM>), and provides the user with the function of performing network setting and the like on the safety device <NUM> which is connected via the subordinate network <NUM>. The setting function provided by the support device <NUM> is described in detail later.

Next, hardware configuration examples of main apparatuses constituting the safety control system <NUM> according to the embodiment are described.

<FIG> is a schematic diagram showing a hardware configuration example of a standard control unit constituting the control device according to the embodiment. With reference to <FIG>, the standard control unit <NUM> includes a processor <NUM>, a main memory <NUM>, a storage <NUM>, a superordinate network controller <NUM>, subordinate network controllers <NUM> and <NUM>, a universal serial bus (USB) controller <NUM>, a memory card interface <NUM>, and an internal bus controller <NUM>. These components are connected via a processor bus <NUM>.

The processor <NUM> corresponds to an arithmetic processing part that executes control arithmetic and the like, and is formed of a central processing unit (CPU), a graphics processing unit (GPU), or the like. Specifically, the processor <NUM> reads out programs (for example, a system program <NUM> and a standard control program <NUM>) stored in the storage <NUM> and develops the programs in the main memory <NUM> for execution, thereby achieving the control corresponding to the control target and a variety of processing.

The main memory <NUM> is formed of a volatile memory apparatus and the like, such as a dynamic random access memory (DRAM) or a static random access memory (SRAM). The storage <NUM> is formed of, for example, a non-volatile memory apparatus and the like, such as a hard disk drive (HDD) or a solid state drive (SSD).

In the storage <NUM>, in addition to the system program <NUM> for achieving basic functions, the standard control program <NUM> created according to the control target such as equipment or a machine is stored. Furthermore, the storage <NUM> stores memory mapping information for relaying the data transmission which is done by the safety control unit <NUM> and in which the superordinate network controller <NUM> and/or the subordinate network controllers <NUM> and <NUM> are/is employed.

The superordinate network controller <NUM> exchanges data with an arbitrary information processing apparatus such as another control device <NUM>, the HMI <NUM>, the server apparatus <NUM>, or the like via the superordinate network <NUM>.

The subordinate network controllers <NUM> and <NUM> exchange data with devices and/or the safety device <NUM> via the subordinate network <NUM>. In <FIG>, two subordinate network controllers <NUM> and <NUM> are shown, but it may also be that only one subordinate network controller is adopted.

The USB controller <NUM> exchanges data with the support device <NUM> and the like via a USB connection.

The memory card interface <NUM> receives a memory card <NUM> which is an example of a detachable recording medium. The memory card interface <NUM> is capable of writing data into the memory card <NUM> and reading various data (log, trace data, and the like) out from the memory card <NUM>.

The internal bus controller <NUM> exchanges data with the safety control unit <NUM> or the safety IO unit <NUM> via an internal bus <NUM>. More specifically, the internal bus controller <NUM> includes a master controller <NUM>, an IO data memory <NUM>, a transmission circuit (TX) <NUM>, and a reception circuit (RX) <NUM>.

The IO data memory <NUM> is a memory that temporarily holds data (input data and output data) exchanged with various units via the internal bus <NUM>, and an address is defined in advance in association with each unit. The transmission circuit <NUM> generates a communication frame including output data and sends out the communication frame to the internal bus <NUM>. The reception circuit <NUM> receives the communication frame transmitted through the internal bus <NUM> and demodulates the communication frame into input data. The master controller <NUM> controls the IO data memory <NUM>, the transmission circuit <NUM>, and the reception circuit <NUM> according to the data transmission timing and the like on the internal bus <NUM>. The master controller <NUM> provides the control as a communication master that manages the data transmission and the like on the internal bus <NUM>.

In <FIG>, a configuration example has been shown in which necessary functions are provided by the processor <NUM> executing the program. However, a dedicated hardware circuit (for example, an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or the like) may be used to implement a part or all of the functions provided. Alternatively, hardware in accordance with a general-purpose architecture (for example, an industrial personal computer based on a general-purpose personal computer) may be used to implement main parts of the standard control unit <NUM>. In this case, a virtualization technology may be used to execute a plurality of operating systems (OSs) having different purposes in parallel, and to execute necessary applications in each OS. Furthermore, a configuration in which the functions of a display device, a support device, and the like are integrated into the standard control unit <NUM> may be employed.

<FIG> is a schematic diagram showing a hardware configuration example of the safety control unit <NUM> constituting the control device <NUM> according to the embodiment. With reference to <FIG>, the safety control unit <NUM> includes a processor <NUM>, a main memory <NUM>, a storage <NUM>, and an internal bus controller <NUM>. These components are connected via a processor bus <NUM>.

The internal bus controller <NUM> functions as a communication slave and provides the same communication interface as those of other units. That is, the internal bus controller <NUM> exchanges data with the standard control unit <NUM> and function units via the internal bus <NUM>.

On the internal bus <NUM>, the safety control unit <NUM> and the safety IO unit <NUM> are daisy-chained. That is, when the internal bus controller <NUM> receives a communication frame from an apparatus existing on the upstream side on the internal bus <NUM>, the internal bus controller <NUM> copies therein all or a part of the data of the communication frame and delivers the data to an apparatus existing on the downstream side. Similarly, when the internal bus controller <NUM> receives a communication frame from the apparatus existing on the downstream side on the internal bus <NUM>, the internal bus controller <NUM> copies therein all or a part of the data of the communication frame and delivers the data to the apparatus existing on the upstream side. The data transmission between the standard control unit <NUM> and the function units and the safety control unit <NUM> is achieved by this sequential delivery of the communication frame.

More specifically, the internal bus controller <NUM> includes a slave controller <NUM>, a buffer memory <NUM>, transmission circuits (TX) <NUM> and <NUM>, and reception circuits (RX) <NUM> and <NUM>.

The buffer memory <NUM> temporarily holds the communication frame transmitted through the internal bus <NUM>. When the reception circuit <NUM> receives the communication frame transmitted through the internal bus <NUM>, the reception circuit <NUM> stores all or a part of the communication frame in the buffer memory <NUM>. The transmission circuit <NUM> sends out the communication frame received by the reception circuit <NUM> to the internal bus <NUM> on the downstream side.

Similarly, when the reception circuit <NUM> receives the communication frame transmitted through the internal bus <NUM>, the reception circuit <NUM> stores all or a part of the communication frame in the buffer memory <NUM>. The transmission circuit <NUM> sends out the communication frame received by the reception circuit <NUM> to the internal bus <NUM> on the downstream side.

The slave controller <NUM> controls the transmission circuits <NUM> and <NUM>, the reception circuits <NUM> and <NUM>, and the buffer memory <NUM> in order to achieve the sequential delivery of the communication frame on the internal bus <NUM>.

The processor <NUM> corresponds to an arithmetic processing part that executes control arithmetic and the like, and is formed of a CPU, a GPU, or the like. Specifically, the processor <NUM> reads out programs (for example, a system program <NUM>, a connection management program <NUM>, and a safety program <NUM>) stored in the storage <NUM> and develops the programs in the main memory <NUM> for execution, thereby achieving the control corresponding to the control target and a variety of processing as described later.

The main memory <NUM> is formed of a volatile memory apparatus and the like, such as a DRAM or a SRAM. The storage <NUM> is formed of, for example, a non-volatile memory apparatus and the like, such as a HDD or a SSD.

In the storage <NUM>, in addition to the system program <NUM> for achieving basic functions, the connection management program <NUM> for establishing and maintaining a connection for data exchange with the safety device <NUM>, master setting information <NUM> that includes setting information required for the data exchange with the safety device <NUM>, and the safety program <NUM> which is created corresponding to the target safety device <NUM> are stored. The master setting information <NUM> includes the connection setting information <NUM> for establishing a connection with the safety device <NUM>.

In <FIG>, a configuration example has been shown in which necessary functions are provided by the processor <NUM> executing the program. However, a dedicated hardware circuit (for example, an ASIC, a FPGA, or the like) may be used to implement a part or all of the functions provided. Alternatively, hardware in accordance with a general-purpose architecture (for example, an industrial personal computer based on a general-purpose personal computer) may be used to implement main parts of the safety control unit <NUM>.

<FIG> is a schematic diagram showing a hardware configuration example of the support device <NUM> connected to the control device <NUM> according to the embodiment. As an example, the support device <NUM> is implemented by using hardware in accordance with a general-purpose architecture (for example, a general-purpose personal computer) to execute the programs.

With reference to <FIG>, the support device <NUM> includes a processor <NUM>, a main memory <NUM>, a storage <NUM>, an input part <NUM>, a display part <NUM>, an optical drive <NUM>, and a USB controller <NUM>. These components are connected via a processor bus <NUM>.

The processor <NUM> is formed of a CPU and the like, reads out programs (for example, the master setting tool <NUM>, the slave setting tools <NUM> to <NUM>, and an OS <NUM>) stored in the storage <NUM> and develops the programs in the main memory <NUM> for execution, thereby implementing a variety of processing described later.

In the storage <NUM>, in addition to the OS <NUM> for achieving basic functions, the master setting tool <NUM> and the slave setting tools <NUM> to <NUM> for providing the function as the support device <NUM> are stored.

The input part <NUM> is formed of a keyboard, a mouse, or the like, and receives user operations. The display part <NUM> is formed of a display, various indicators, a printer, and the like, and outputs processing results and the like from the processor <NUM>. The input part <NUM> and the display part <NUM> constitute a user interface of the support device <NUM>.

The USB controller <NUM> controls the data exchange with the standard control unit <NUM> of the control device <NUM> and the like via a USB connection.

The support device <NUM> has the optical drive <NUM>. From a recording medium <NUM> (for example, an optical recording medium such as a digital versatile disc (DVD)) which stores computer-readable programs in a non-transitory manner, the programs stored therein are read out to be installed in the storage <NUM> and the like.

The programs executed in the support device <NUM> may be installed via the recording medium <NUM> that is computer-readable, or may be installed in a form of being downloaded from a server apparatus and the like on the network. In addition, the function provided by the support device <NUM> according to the embodiment may also be achieved in a form of employing a part of a module provided by the OS.

In <FIG>, a configuration example has been shown in which necessary functions as the support device <NUM> are provided by the processor <NUM> executing the program. However, a dedicated hardware circuit (for example, an ASIC, a FPGA, or the like) may be used to implement a part or all of the functions provided.

The safety IO unit <NUM> is an example of a function unit connected to the standard control unit <NUM> via the internal bus <NUM>, and performs the signal input from the safety device <NUM> and/or the signal output to the safety device <NUM>. Compared with a standard IO unit, the safety IO unit <NUM> is equipped with signal input/output and signal management functions required for achieving the safety of feedback signals and the like. The hardware configuration of the safety IO unit <NUM> is publicly known, and thus more detailed description is not performed.

The HMI <NUM> may employ a hardware configuration mounted as a dedicated machine or employ a hardware configuration in accordance with a general-purpose architecture (for example, an industrial personal computer based on a general-purpose personal computer). When the HMI <NUM> is implemented by an industrial personal computer based on a general-purpose personal computer, the same hardware configuration as that of the support device <NUM> as shown in <FIG> described above is employed.

As an example, the server apparatus <NUM> can be implemented using a general-purpose file server or a database server. The hardware configuration of this apparatus is publicly known, and thus more detailed description is not performed.

Next, the communication between the safety control unit <NUM> and the safety device <NUM> is described.

<FIG> is a schematic diagram for describing the data transmission between the safety control unit and the safety device in the safety control system according to the embodiment. With reference to <FIG>, when acquiring input data from the safety devices <NUM>-<NUM>, <NUM>-<NUM>, and <NUM>-<NUM>, or giving arbitrary output to the safety devices <NUM>-<NUM>, <NUM>-<NUM>, and <NUM>-<NUM>, the safety control unit <NUM> performs one type of message transmission communication with each of the safety devices <NUM>-<NUM>, <NUM>-<NUM>, and <NUM>-<NUM>.

As shown in <FIG>, a connection <NUM> for performing message transmission between the safety control unit <NUM> and the safety device <NUM>-<NUM>, a connection <NUM> for performing message transmission between the safety control unit <NUM> and the safety device <NUM>-<NUM>, and a connection <NUM> for performing message transmission between the safety control unit <NUM> and the safety device <NUM>-<NUM> are respectively established.

The safety control unit <NUM> functions as a communication master and is also referred to as an "originator". The safety device <NUM> functions as a communication slave and is also referred to as a "target".

In this kind of message transmission, identification information such as an IP address, a safety network number (SNN), an originator unique network identifier (OUNID), a target unique network identifier (TUNID), a safety configuration identifier (SCID), attribute information, and the like are used in the connection establishment and message exchange.

Each of the safety devices <NUM>-<NUM>, <NUM>-<NUM>, and <NUM>-<NUM> holds slave setting information <NUM>. The slave setting information <NUM> includes an IP address <NUM>, a TUNID <NUM>, a SCID <NUM>, and attribute information <NUM>.

The slave setting information <NUM> is set by the support device <NUM> (see <FIG>). For example, the user activates the slave setting tool <NUM> (see <FIG> and <FIG>) of the support device <NUM>, and inputs the IP address, the TUNID, and attribute information of the safety device <NUM>-<NUM> in a setting screen displayed by the execution of the slave setting tool <NUM>. Moreover, because the TUNID is a data string in which the IP address and the SNN are combined, the user may input the SNN instead of the TUNID. The support device <NUM> determines the input IP address, TUNID, and attribute information as the IP address <NUM>, the TUNID <NUM>, and the attribute information <NUM> of the slave setting information <NUM> according to a command of the slave setting tool <NUM>.

As described above, when the setting of the safety device <NUM>-<NUM> using the slave setting tool <NUM> is completed, the SCID <NUM> is generated by combining the SCCRC corresponding to the setting data and the SCTC which is a time stamp.

The support device <NUM> sets, in the slave setting information <NUM> of the safety device <NUM>-<NUM>, the determined IP address <NUM>, TUNID <NUM>, and attribute information <NUM>, and the generated SCID <NUM>. In other words, the support device <NUM> updates the slave setting information <NUM> of the safety device <NUM>-<NUM> by using the determined IP address <NUM>, TUNID <NUM>, and attribute information <NUM>, and the generated SCID <NUM>.

Similarly, the support device <NUM> sets the slave setting information <NUM> of the safety devices <NUM>-<NUM> and <NUM>-<NUM> by the execution of the slave setting tools <NUM> and <NUM>, respectively.

On the other hand, the safety control unit <NUM> has the master setting information <NUM> for performing communication with each safety device <NUM>. The master setting information <NUM> includes, in addition to an OUNID <NUM> which is identification information of the safety control unit <NUM>, connection setting information <NUM>-<NUM> to <NUM>-<NUM> (hereinafter, also collectively referred to as "connection setting information <NUM>").

The connection setting information <NUM>-<NUM> to <NUM>-<NUM> respectively correspond to the safety devices <NUM>-<NUM> to <NUM>-<NUM>. The connection setting information <NUM> includes an IP address <NUM>, a TUNID <NUM>, a SCID <NUM>, and attribute information <NUM> of the corresponding safety device <NUM>.

The connection setting information <NUM> is set by the support device <NUM>. For example, the user activates the master setting tool <NUM> (see <FIG> and <FIG>) of the support device <NUM>, and inputs the IP address, TUNID, and attribute information of the safety device <NUM> in a setting screen displayed by the execution of the master setting tool <NUM>. Moreover, because the TUNID is a data string in which the IP address and the SNN are combined, the user may input the SNN instead of the TUNID. The support device <NUM> determines the input IP address, TUNID, and attribute information of the safety device <NUM> as the IP address <NUM>, the TUNID <NUM>, and the attribute information <NUM> of the connection setting information <NUM> according to a command of the master setting tool <NUM>.

The support device <NUM> sets the connection setting information <NUM> of the safety control unit <NUM> by using the determined IP address <NUM>, TUNID <NUM>, and attribute information <NUM>. In other words, the support device <NUM> updates the connection setting information <NUM> of the safety control unit <NUM> by using the determined IP address <NUM>, TUNID <NUM>, and attribute information <NUM>.

The support device <NUM> also holds the set IP address <NUM>, TUNID <NUM>, and attribute information <NUM> therein in correspondence with the safety device <NUM>.

Furthermore, the support device <NUM> sets the SCID <NUM> of the connection setting information <NUM> according to a command of the master setting tool <NUM>. The setting method is described later.

<FIG> is a schematic diagram showing a method for establishing a connection between the safety control unit and the safety device in accordance with "Type 2a".

With reference to <FIG>, for example, the safety control unit <NUM> sends a message including a command such as "Safety Open" to the safety device <NUM>. The data format of the message includes the OUNID <NUM> of the safety control unit <NUM>, the TUNID <NUM> and the SCID <NUM> included in the connection setting information <NUM> corresponding to the safety device <NUM>, a connection parameters cyclic redundancy check (CPCRC) for checking errors that may occur in the TUNID <NUM> and the OUNID <NUM>, entity data (Data), and a data cyclic redundancy check (Data CRC) for checking errors that may occur in the entity data (a case of message (i)).

Alternatively, when there is no entity data to be transmitted, a simplified data format of the message may be employed. The data format includes the OUNID <NUM> of the safety control unit <NUM>, the TUNID <NUM> and the SCID <NUM> included in the connection setting information <NUM> corresponding to the safety device <NUM>, and the CPCRC for checking errors that may occur in the TUNID <NUM> and the OUNID <NUM> (a case of message (ii)).

When receiving the message (i) or (ii) from the safety control unit <NUM>, each safety device <NUM> compares the message respectively with the TUNID <NUM> and the SCID <NUM> of the slave setting information <NUM> held by the device itself. Then, when the TUNID and the SCID in the message match the TUNID <NUM> and the SCID <NUM> in the slave setting information <NUM> respectively, a judgment is made that the message to the device itself is correctly received, and the connection with the safety control unit <NUM> is established.

Moreover, when "Type 2b" is selected, the data format of the message with the SCID omitted is employed. In this case, the comparison of the TUNID included in the message with the TUNID <NUM> in the slave setting information <NUM> becomes main verification processing.

As described above, in the safety control system <NUM> according to the embodiment, the safety control unit <NUM> is required to hold the SCID <NUM> which is the same as the SCID <NUM> set in the safety device <NUM> to which a connection is established according to "Type 2a".

As described above, the safety control unit <NUM> and the safety device <NUM> are required to hold the same SCID in order to establish a connection. The SCID <NUM> held by the safety device <NUM> is updated every time the setting of the safety device <NUM> is revised. Therefore, when the setting of the safety device <NUM> is revised, the SCID <NUM> of the connection setting information <NUM> held by the safety control unit <NUM> is also required to be reset.

<FIG> is a schematic diagram showing an example of a functional configuration of the support device. In <FIG>, a configuration regarding the setting of the SCID <NUM> for the safety control unit <NUM> is shown. As shown in <FIG>, the support device <NUM> includes a master setting part <NUM> that performs the setting of the safety control unit <NUM>. The master setting part <NUM> is implemented by the processor <NUM> shown in <FIG> executing the master setting tool <NUM>.

The master setting part <NUM> displays a setting screen on the display part <NUM> (see <FIG>), and performs the setting of the safety control unit <NUM> according to the input to the input part <NUM>.

<FIG> is a diagram showing an example of the setting screen for setting the safety control unit. A setting screen <NUM> illustrated in <FIG> is a screen for performing the setting regarding the establishment of a connection with the safety device <NUM>. The master setting part <NUM> displays the setting screen <NUM> on the display part <NUM> for each safety device <NUM> network-connected to the safety control unit <NUM>.

The setting screen <NUM> includes radio buttons <NUM> and <NUM> for selecting the establishment method of the connection. The radio button <NUM> is a button for selecting "Type 2a", and the radio button <NUM> is a button for selecting "Type 2b". The user may operate either the radio button <NUM> or the radio button <NUM> in accordance with the safety device <NUM>.

The setting screen <NUM> further includes a button <NUM> for acquiring the SCID <NUM> from the safety device <NUM>. The master setting part <NUM> receives the pressing of the button <NUM> only when the radio button <NUM> is operated.

The setting screen <NUM> further includes a button <NUM> for setting the SCID <NUM> acquired from the safety device <NUM> in the connection setting information <NUM>.

Returning to <FIG>, the master setting part <NUM> has a SCID acquisition part <NUM> and a SCID setting part <NUM>. The SCID acquisition part <NUM> starts the following processing in response to the pressing of the button <NUM> on the setting screen <NUM>. The SCID setting part <NUM> starts the following processing in response to the pressing of the button <NUM> on the setting screen <NUM>.

The SCID acquisition part <NUM> acquires the SCID <NUM> stored in the memory part <NUM> of the safety device <NUM>. Specifically, the SCID acquisition part <NUM> generates a command (or a message) for requesting the SCID <NUM>. The command is defined in CIP Safety. The SCID acquisition part <NUM> acquires the SCID <NUM> from the safety device <NUM> by outputting the generated command to the safety device <NUM> via the safety control unit <NUM>. Alternatively, the SCID acquisition part <NUM> may instruct the safety control unit <NUM> to generate and output the command for requesting the SCID <NUM>. The safety control unit <NUM> acquires the SCID <NUM> from the safety device <NUM> and delivers the acquired SCID <NUM> to the support device <NUM> according to the instruction.

The SCID acquisition part <NUM> displays the value of the SCID <NUM> acquired from the safety device <NUM> in an area <NUM> (see <FIG>) of the setting screen <NUM>.

The SCID setting part <NUM> determines the SCID <NUM> acquired from the safety device <NUM> as the SCID <NUM> of the connection setting information <NUM>. The SCID setting part <NUM> sets the determined SCID <NUM> in the connection setting information <NUM> of the safety control unit <NUM>.

<FIG> is a flowchart showing an example of setting processing of the SCID for the safety control unit. Steps S1 to S7 shown in <FIG> are executed in response to the pressing of the button <NUM> on the setting screen <NUM> shown in <FIG>. Steps S1 to S7 are executed according to the commands of the master setting tool <NUM>. Steps S1 to S7 are executed for each safety device <NUM>. Hereinafter, the processing for the safety device <NUM>-<NUM> is described.

The processor <NUM> executes a command (C) of the master setting tool <NUM>. The command (C) is a command for acquiring the TUNID <NUM> from the safety device <NUM>-<NUM> which is an actual machine. The processor <NUM> acquires the TUNID <NUM> from the safety device <NUM>-<NUM> by executing the command (C) (step S1). Specifically, the processor <NUM> generates a command for requesting the TUNID <NUM>, and outputs the generated command to the safety device <NUM>-<NUM> via the safety control unit <NUM>, thereby acquiring the TUNID <NUM> from the safety device <NUM>-<NUM>. The command is defined in CIP. Alternatively, the processor <NUM> may instruct the safety control unit <NUM> to generate and output the command for requesting the TUNID <NUM>. The safety control unit <NUM> acquires the TUNID <NUM> from the safety device <NUM>-<NUM> and delivers the acquired TUNID <NUM> to the support device <NUM> according to the instruction.

Next, the processor <NUM> executes a command (D) of the master setting tool <NUM>. The command (D) is a command for comparing the acquired TUNID <NUM> with the TUNID <NUM> held in association with the safety device <NUM>-<NUM>. The processor <NUM> judges whether or not the TUNID <NUM> and the TUNID <NUM> match with each other by executing the command (D) (step S2). As described above, the TUNID <NUM> is set in the connection setting information <NUM>-<NUM> according to the command of the master setting tool <NUM> and is held in the support device <NUM>. When the TUNID <NUM> and the TUNID <NUM> do not match with each other (NO in step S2), the processor <NUM> ends the processing.

When the TUNID <NUM> and the TUNID <NUM> match with each other (YES in step S2), the processor <NUM> executes a command (E) of the master setting tool <NUM>. The command (E) is a command for acquiring the attribute information <NUM> from the safety device <NUM>-<NUM> which is an actual machine. The processor <NUM> acquires the attribute information <NUM> from the safety device <NUM>-<NUM> by executing the command (E) (step S3). Specifically, the processor <NUM> generates a command for requesting the attribute information <NUM>, and outputs the generated command to the safety device <NUM>-<NUM> via the safety control unit <NUM>, thereby acquiring the attribute information <NUM> from the safety device <NUM>-<NUM>. The command is defined in CIP. Alternatively, the processor <NUM> may instruct the safety control unit <NUM> to generate and output the command for requesting the attribute information <NUM>. The safety control unit <NUM> acquires the attribute information <NUM> from the safety device <NUM>-<NUM> and delivers the acquired attribute information <NUM> to the support device <NUM> according to the instruction.

Next, the processor <NUM> executes a command (F) of the master setting tool <NUM>. The command (F) is a command for comparing the acquired attribute information <NUM> with the attribute information <NUM> held in association with the safety device <NUM>-<NUM>. The processor <NUM> judges whether or not the attribute information <NUM> and the attribute information <NUM> match with each other by executing the command (F) (step S4). As described above, the attribute information <NUM> is set in the connection setting information <NUM>-<NUM> according to the command of the master setting tool <NUM> and is held in the support device <NUM>. When the attribute information <NUM> and the attribute information <NUM> do not match with each other (NO in step S4), the processor <NUM> ends the processing.

When the attribute information <NUM> and the attribute information <NUM> match with each other (YES in step S4), the processor <NUM> acquires the SCID <NUM> from the safety device <NUM>-<NUM> which is an actual machine by executing the above command (A) of the master setting tool <NUM> (step S5). The processor <NUM> judges whether or not there is an instruction to reflect the acquired SCID <NUM> in the safety control unit <NUM> of the control device <NUM> (step S6). Specifically, the processor <NUM> judges that there is a reflection instruction in response to the pressing of the button <NUM> on the setting screen <NUM>. When there is no reflection instruction (NO in step S6), the processor <NUM> ends the processing.

When there is a reflection instruction (YES in step S6), the processor <NUM> determines the acquired SCID <NUM> as the SCID <NUM> of the connection setting information <NUM>-<NUM> by executing the above command (B) of the master setting tool <NUM>. Then, the processor <NUM> sets the determined SCID <NUM> (that is, the acquired SCID <NUM>) in the connection setting information <NUM>-<NUM> (step S7).

In the above description, the master setting part <NUM> displays the setting screen <NUM> (see <FIG>) on the display part <NUM> for each safety device <NUM>, and sets the SCID <NUM> of the connection setting information <NUM> according to the input to the setting screen <NUM>. However, the master setting part <NUM> may display, on the display part <NUM>, a setting screen for collectively setting the SCID <NUM> of the connection setting information <NUM> corresponding to a plurality of safety devices <NUM>.

<FIG> is a diagram showing another example of a setting screen for setting the safety control unit. A setting screen <NUM> illustrated in <FIG> is a screen for collectively setting the SCID <NUM> of the connection setting information <NUM> corresponding to a plurality of safety devices <NUM>.

The setting screen <NUM> includes a device list <NUM> showing a listing of a plurality of safety devices <NUM> connected to the safety control unit <NUM>. The device list <NUM> has four columns <NUM> to <NUM>.

The safety device name is displayed in the column <NUM>. The IP address is displayed in the column <NUM>.

An input field <NUM> of the SCID is displayed in the column <NUM>. The user can input the SCID in the input field <NUM>.

In the column <NUM>, a switch button <NUM> for selecting the establishment method of the connection is displayed. The switch button <NUM> is a button for switching the establishment method of the connection to either "Type 2a" or "Type 2b". The user can switch the establishment method of the connection between each safety device <NUM> and the safety control unit <NUM> by operating the switch button <NUM> for each safety device <NUM>.

In the method of "Type 2b", a check using the SCID is not performed. Therefore, when "Type 2b" is selected in the column <NUM>, the input field <NUM> is not displayed in the column <NUM>.

Furthermore, the setting screen <NUM> includes a collective switching button <NUM>, a check box <NUM>, and an OK button <NUM>.

The collective switching button <NUM> is a button for collectively switching all the switch buttons <NUM> in the column <NUM> of the device list <NUM> to either "Type 2a" or "Type 2b". For example, if the collective switching button <NUM> is pressed in a state that the switch button <NUM> indicating "Type 2a" and the switch button <NUM> indicating "Type 2b" coexist, all the switch buttons <NUM> in the column <NUM> are switched to "Type 2a". If the collective switching button <NUM> is pressed in a state that all the switch buttons <NUM> in the column <NUM> indicate "Type 2a", all the switch buttons <NUM> in the column <NUM> are switched to "Type 2b". If the collective switching button <NUM> is pressed in a state that all the switch buttons <NUM> in the column <NUM> indicate "Type 2b", all the switch buttons <NUM> in the column <NUM> are switched to "Type 2a". Thereby, the user can collectively switch the establishment method of the connection between the plurality of safety devices <NUM> and the safety control unit <NUM>.

The check box <NUM> is checked when the SCID <NUM> of the connection setting information <NUM> is automatically set for the safety device <NUM> in which the switch button <NUM> is set to "Type 2a".

The OK button <NUM> is a button for starting the setting of the SCID <NUM> to the connection setting information <NUM> of the safety control unit <NUM>.

In order to save the trouble of inputting the SCID in the input field <NUM>, the user may check the check box <NUM> and press the OK button <NUM>.

<FIG> is a flowchart showing another example of the setting processing of the SCID for the safety control unit. Steps S11 to S15 shown in <FIG> are executed in response to the fact that the OK button <NUM> is pressed while the check box <NUM> on the setting screen <NUM> shown in <FIG> is checked. Steps S11 to S15 are executed according to the commands of the master setting tool <NUM>.

The processor <NUM> executes a command (G) of the master setting tool <NUM>. The command (G) is a command for setting either "Type 2a" or "Type 2b" for each of a plurality of safety devices <NUM> according to the input to the switch button <NUM>. By executing the command (G), the processor <NUM> sets either "Type 2a" or "Type 2b" as the establishment method of the connection between each safety device <NUM> and the safety control unit <NUM> according to the input to the switch button <NUM> (step S11).

Next, the processor <NUM> specifies the safety device <NUM> for which "Type 2a" has been set as the safety device <NUM> in which the SCID <NUM> is automatically set (step S12). Next, the processor <NUM> executes a SCID collective setting loop of steps S13 to S <NUM>. That is, the processor <NUM> repeats step S14 for each safety device <NUM> specified in step S <NUM>. The subroutine in step S14 is executed according to the flowchart shown in <FIG>. However, step S6 is omitted. When step S14 is completed for all the safety devices <NUM> specified in step S12, the processor <NUM> ends the processing.

In this way, by merely checking the check box <NUM> and then pressing the OK button <NUM>, the user can collectively set the SCID <NUM> in the connection setting information <NUM> of the safety control unit <NUM> for all of the plurality of safety devices <NUM>.

Moreover, the processor <NUM> may exclude the safety device <NUM> for which the SCID is input in the input field <NUM> in step S12. Specifically, the processor <NUM> may execute a command (H) of the master setting tool <NUM> in step S12. The command (H) is a command for classifying, according to whether or not the SCID is input to the input field <NUM>, each safety device <NUM> for which "Type 2a" is set into either a first group in which the SCID <NUM> is automatically set or a second group in which the SCID <NUM> is manually set. By executing the command (H), the processor <NUM> classifies the safety device <NUM> for which the SCID has not input to the input field <NUM> into the first group. Then, in step S12, the processor <NUM> may specify the safety device <NUM> belonging to the first group as the safety device <NUM> in which the SCID <NUM> is automatically set.

The master setting tool <NUM> may also be installed on the HMI <NUM>. Thereby, the user can set the connection setting information <NUM> of the safety control unit <NUM> by using the HMI <NUM>.

As described above, the support device <NUM> is capable of communicating with the control device <NUM> network-connected to one or a plurality of safety devices <NUM>. Each of the one or plurality of safety devices <NUM> holds the setting identification information (the SCID <NUM>) that identifies the setting of the own device. The control device <NUM> holds, for each of the one or plurality of safety devices <NUM>, the connection setting information <NUM> set for establishing a connection with the safety device. The one or plurality of safety devices <NUM> include a target safety device for which "Type 2a" (a first establishment method) has been set, wherein "Type 2a" establishes a connection with the control device <NUM> in accordance with the result of comparison between the connection setting information <NUM> and the SCID <NUM>. The support device <NUM> includes the storage <NUM> in which the master setting tool <NUM> that assists in the setting of the control device <NUM> is stored, and the processor <NUM> for executing the master setting tool <NUM>. The master setting tool <NUM> includes the command (A) and the command (B). The command (A) is a command for acquiring the SCID <NUM> from the target safety device. The command (B) is a command for setting the SCID <NUM> acquired from the target safety device in response to the execution of the command (A) as the SCID <NUM> of the connection setting information <NUM> corresponding to the target safety device.

According to the above configuration, the user can save the trouble of activating the slave setting tools <NUM> to <NUM> and recording the SCID <NUM> for identifying the setting of the safety device on a memo paper or the like as in the conventional case. As a result, even when multiple safety devices <NUM> are connected to the same network, the user can easily set the SCID that identifies the setting of each of the multiple safety devices <NUM> in the control device <NUM>.

Each of the one or plurality of safety devices <NUM> holds the TUNID <NUM>, which is device identification information for identifying the own device. The master setting tool <NUM> further includes the command (C) and the command (D). The command (C) is a command for acquiring the TUNID <NUM> from the target safety device. The command (D) is a command for comparing the TUNID <NUM> acquired from the target safety device in response to the execution of the command (C) with the TUNID <NUM> held in association with the target safety device. The command (A) and the command (B) are executed according to the fact that the comparison result obtained by executing the command (D) shows a match.

According to the above configuration, it is possible to suppress erroneous setting of the SCID in the connection setting information.

Each of the one or plurality of safety devices <NUM> holds the attribute information <NUM> representing the attribute of the own device. The master setting tool <NUM> further includes the command (E) and the command (F). The command (E) is a command for acquiring the attribute information <NUM> from the target safety device. The command (F) is a command for comparing the attribute information <NUM> acquired from the target safety device in response to the execution of the command (E) with the attribute information <NUM> held in association with the target safety device. The command (A) and the command (B) are executed according to the fact that the comparison result obtained by executing the command (F) shows a match.

The support device <NUM> includes the input part <NUM> and the display part <NUM>, which constitute the user interface. The master setting tool <NUM> may further include the command (G) for setting either "Type 2a" or "Type 2b" (a second establishment method) for each of the one or plurality of safety devices <NUM> according to the input to the input part <NUM>, wherein "Type 2b" establishes a connection with the control device <NUM> without using the SCID. The target safety device is a safety device for which "Type 2a" has been set by executing the command (G).

According to the above configuration, the command (A) is executed only for the safety device in which the SCID is required for establishing the connection. Thereby, unnecessary communication can be suppressed in the setting of the control device <NUM>.

The master setting tool <NUM> may further include the command (H) for classifying, according to the input to the input part <NUM>, each of the one or plurality of safety devices <NUM> into either the first group in which the SCID is automatically set or the second group in which the connection setting information is manually set. The target safety device is a safety device classified into the first group by executing the command (H).

According to the above configuration, the command (A) is not executed for the safety device in which the SCID is manually set for the controller <NUM>. Thereby, unnecessary communication can be suppressed in the setting of the control device <NUM>.

Claim 1:
A support device (<NUM>) capable of communicating with a control device (<NUM>) network-connected to one or a plurality of safety devices (<NUM>), wherein
each of the one or plurality of safety devices (<NUM>) is configured to hold setting identification information (<NUM>) that identifies the setting of the own device;
the control device (<NUM>) is configured to hold, for each of the one or plurality of safety devices (<NUM>), connection setting information (<NUM>) set for establishing a connection with the safety device (<NUM>);
the one or plurality of safety devices (<NUM>) include a target safety device (<NUM>) for which a first establishment method has been set, wherein the first establishment method establishes a connection with the control device (<NUM>) in accordance with a result of a comparison between the connection setting information (<NUM>) and the setting identification information (<NUM>);
the support device (<NUM>) is characterized by comprising:
a memory part (<NUM>) for storing a support program (<NUM>) that is configured to assist in the setting of the control device (<NUM>); and
a processor (<NUM>) for executing the support program (<NUM>); and
the support program (<NUM>) comprises:
a first command for acquiring the setting identification information (<NUM>) from the target safety device (<NUM>); and
a second command for setting, in the connection setting information (<NUM>) corresponding to the target safety device (<NUM>), the setting identification information (<NUM>) acquired from the target safety device (<NUM>) in response to the execution of the first command.