Patent Description:
Conventionally, a system including a device and a slave device having a communication port to which the device is connected is known. Patent Literature <NUM> discloses a slave device that acquires the identification information of the device from the device connected to a communication port in the system and generates, on the basis of the acquired identification information, the configuration settings information including information of the device to be connected to the communication port. <CIT> relates to an EtherCAT fieldbus system, a master and a slave for the system and a method. The slave is configured to be coupled to the EtherCAT fieldbus. A first configurable memory of the slave stores a first activation list indicating for consecutive bytes of data of an EtherCAT datagram a corresponding fieldbus memory management information or synchronization management information.

The system as described above has a superordinate device that controls the entire system, and a slave device is connected to the superordinate device. Settings according to the connected device are required not only for the slave device but also for the superordinate device that communicates with the slave device. Specifically, the superordinate device needs to be set according to the device regarding the storage region of data exchanged with the device via the slave device. However, even with the above-mentioned conventional technology, the settings in the superordinate device needs to be made manually, and such work takes time.

One aspect of the invention is to reduce the steps for setting the device in the superordinate device that communicates with the slave device having the communication port to which the device is connected.

In order to solve the above problems, the invention provides a settings information generation device, generating settings information of a superordinate device that communicates with a slave device including a communication port to which the device is connected, the settings information generation device including a selection unit for accepting a selection of the device to be connected from a user; an acquisition unit for acquiring operational settings information including an input/output data length of the selected device; and a generation unit for generating, on the basis of the operational settings information, superordinate device settings information that sets a storage region in the superordinate device in which the superordinate device stores data exchanged with the device via the slave device.

In order to solve the above problems, the invention provides a settings information generation method generating, settings information of a superordinate device that communicates with a slave device including a communication port to which the device is connected, the settings information generation method including: a selection step, accepting a selection of the device to be connected from a user; an acquisition step, acquiring an operational settings information including an input/output data length of the selected device; and a generation step, generating, on the basis of the operational settings information, superordinate device settings information that sets a storage region in the superordinate device in which the superordinate device stores data exchanged with the device via the slave device.

According to one aspect of the invention, it is possible to reduce the steps for setting the device in the superordinate device that communicates with the slave device having the communication port to which the device is connected.

Hereinafter, each embodiment (hereinafter, also referred to as "the present embodiment") according to one aspect of the invention will be described with reference to the drawings.

<FIG> is a block diagram showing a configuration of an information processing system <NUM> as an example of a system to which a settings information generation device <NUM> according to the present embodiment is applied. In <FIG>, an information processing system <NUM> includes the settings information generation device <NUM> and a control system <NUM>. The settings information generation device <NUM> is communicably connected to a controller <NUM> and a communication coupler <NUM>, which will be described later, included in the control system <NUM>.

The control system <NUM> includes the controller <NUM>, the communication coupler <NUM>, device management units 50_1 to 50_3, and devices 60_1 to 60_3, 60_4 to 60_6, and 60_7 to 60_9. The controller <NUM> and the communication coupler <NUM> correspond to an example of the superordinate device in the invention. The device management units 50_1 to 50_3 correspond to an example of the slave device in the invention.

The device management units 50_1 to 50_3 are connected to the controller <NUM>. Each of the one or more communication ports of the device management units 50_1 to 50_3 is connected to one of the devices 60_1 to 60_9. The device management units 50_1 to 50_3 manage the input/output of data to and from the devices 60_1 to 60_9. The controller <NUM> communicates with each device management unit <NUM> to control the entire control system <NUM>. Hereinafter, when it is not necessary to distinguish between the device management units 50_1 to 50_3, each of them is also simply referred to as the device management unit <NUM>. When it is not necessary to distinguish between the devices 60_1 to 60_1, each is also simply referred to as device <NUM>. The number of each device included in the control system <NUM>, the network configuration for connecting each device, and the number of communication ports of the device management unit <NUM> are not limited to the illustrated examples.

For example, the control system <NUM> may be an IO-Link (registered trademark) system. In this case, the device <NUM> is an IO-Link device corresponding to the IO-Link interface, for example, a sensor, an actuator, or the like. Moreover, the device management unit <NUM> is an IO-Link master that performs point-to-point communication with the IO-Link device. Communication is performed with IO-Link between the device management unit <NUM> and the device <NUM>. Further, the controller <NUM> is realized by a PLC (Programmable Logic Controller). Details of IO-Link will be described later.

The connection form of the device management unit <NUM> in the control system <NUM> is various. For example, the device management unit 50_1 is connected to the controller <NUM> via a bus <NUM>. The data output from the devices 60_1 to 60_3 is input to the device management unit 50_1 and transmitted from the device management unit 50_1 to the controller <NUM> via the bus <NUM>. The data for the controller <NUM> to control the devices 60_1 to 60_3 is transmitted from the controller <NUM> to the device management unit 50_1 via the bus <NUM>, and is input from the device management unit 50_1 to the devices 60_1 to 60_3. The superordinate device of the device management unit 50_1 is the controller <NUM>.

Further, the device management unit 50_2 s connected to the controller <NUM> via a field network <NUM>. The data output from the devices 60_4 to 60_6 is input to the device management unit 50_2, and is transmitted from the device management unit 50_2 to the controller <NUM> via the field network <NUM>. The data for the controller <NUM> to control the devices 60_4 to 60_6 is transmitted from the controller <NUM> to the device management unit 50_2 via the field network <NUM>, and is input from the device management unit 50_2 to the devices 60_4 to 60_6. The superordinate device of the device management unit 50_2 is the controller <NUM>.

Further, the device management unit 50_3 is connected to the controller <NUM> via the communication coupler <NUM> connected to the field network <NUM>. The data output from the devices 60_7 to 60_9 is input to the device management unit 50_3, transmitted from the device management unit 50_3 to the communication coupler <NUM>, and transmitted from the communication coupler <NUM> to the controller <NUM> via the field network <NUM>. The data for the controller <NUM> to control the devices 60_7 to 60_9 is transmitted from the controller <NUM> to the communication coupler <NUM>, transmitted from the communication coupler <NUM> to the device management unit 50_3, and input from the device management unit 50_3 to the devices 60_6 to 60_9. The superordinate device of the device management unit 50_3 is the communication coupler <NUM>.

In the controller <NUM> and the communication coupler <NUM> as superordinate devices, it is necessary to set the storage region of data input from/output to the device <NUM> via the device management unit <NUM>. For example, in the controller <NUM> and the communication coupler <NUM>, it is necessary to allocate the IO memory according to the input/output data length of the device <NUM> connected to subordinate. The IO memory is a storage unit of a transfer destination to which the device management unit <NUM> transfers data input from the device <NUM>. The IO memory has a storage region. In the controller <NUM> and the communication coupler <NUM>, it is necessary to allocate a storage region for each device <NUM> connected to the subordinate such that a capacity corresponding to the input/output data length is secured.

In the device management unit <NUM> as a slave device, it is necessary to set the storage region of data input from/output to the connected device <NUM>. For example, in the device management unit <NUM>, it is necessary to set the input/output data length of the device <NUM> connected to each communication port. Further, in the device management unit <NUM>, it is necessary to set the identification information of the device <NUM> connected to each communication port in order to execute the collation process described later.

The settings information generation device <NUM> generates, on the basis of the operational settings information <NUM> corresponding to the device <NUM>, superordinate device settings information. The superordinate device settings information includes information on a storage region of data exchanged with the device <NUM> via the device management unit <NUM> in each of the controller <NUM> and the communication coupler <NUM>. Further, the settings information generation device <NUM> transmits the superordinate device settings information to the controller <NUM> and the communication coupler <NUM>, and causes each device to automatically execute the settings process.

Further, the settings information generation device <NUM> generates, on the basis of the operational settings information <NUM> corresponding to the device <NUM>, slave device settings information. The slave device settings information includes information on a storage region of data input from/output to the device <NUM> in the device management unit <NUM>. Further, the settings information generation device <NUM> transmits the generated slave device settings information to the device management unit <NUM>, and causes the device to automatically execute the settings process.

In the control system <NUM>, the controller <NUM>, the communication coupler <NUM>, and the device management unit <NUM> need to be set according to each device <NUM> as many as the number of the devices <NUM> to be included in the control system <NUM>. Manually performing such settings is a complicated task for the user and requires a lot of settings steps. The manual operation means that the user refers to the manual of the device and inputs information on the storage region for each device by using, for example, a tool for manually setting. The settings information generation device <NUM> generates the superordinate device settings information and the slave device settings information by using the operational settings information <NUM> corresponding to each device <NUM>, thereby eliminating the need for such manual settings work and significantly reducing the settings steps.

<FIG> is a block diagram showing an example of a detailed configuration of the settings information generation device <NUM>. In <FIG>, the settings information generation device <NUM> includes a control unit <NUM>, a storage unit <NUM>, and a communication unit <NUM>. The settings information generation device <NUM> may be realized by a computer including a memory and a processor. Further, an output device <NUM> and an input device <NUM> are connected to the settings information generation device <NUM>. As the output device <NUM>, for example, a display, a printer, a speaker, or a combination thereof is used. As the input device <NUM>, for example, a keyboard, a mouse, a touch pad, a microphone, or a combination thereof or the like is used. Further, the settings information generation device <NUM> is connected to the controller <NUM> and the communication coupler <NUM> via a network <NUM>. The network <NUM> may be the field network <NUM> or a network different from the field network <NUM>.

The control unit <NUM> controls the operation of the settings information generation device <NUM> in an integrated manner. The control unit <NUM> is composed of a processor included in the computer. The control unit <NUM> functions as a selection unit <NUM>, an acquisition unit <NUM>, and a generation unit <NUM> by reading a control program described later from the storage unit <NUM> and executing the control program. Details of the selection unit <NUM>, the acquisition unit <NUM>, and the generation unit <NUM> will be described later.

The storage unit <NUM> is composed of a memory owned by a computer. The storage unit <NUM> stores multiple operational settings information <NUM>. Each of the multiple operational settings information <NUM> corresponds to any one of the multiple candidates of the device <NUM> that may be connected. Further, the storage unit <NUM> stores a control program for causing the settings information generation device <NUM> to function as the selection unit <NUM>, the acquisition unit <NUM>, and the generation unit <NUM>.

The communication unit <NUM> is a communication module connected to the network <NUM>.

The selection unit <NUM> accepts the selection of the device <NUM> to be connected from the user. Specifically, the selection unit <NUM> presents multiple candidates of the connected device <NUM> to the user by outputting them to the output device <NUM>. For example, the multiple candidates may be displayed on a display as an example of the output device <NUM>. The selection unit <NUM> accepts the selection of the device <NUM> to be connected from the multiple presented candidates via the input device <NUM>. For example, when the selection unit <NUM> accepts an operation in the output device <NUM> of pointing to a region in which any of a multiple candidates is displayed by the mouse as an example of the input device <NUM>, the selection unit <NUM> selects the device <NUM> indicated by the candidate displayed in the region.

The acquisition unit <NUM> acquires the operational settings information <NUM> corresponding to the device <NUM> selected by the selection unit <NUM> from the storage unit <NUM>. The operational settings information <NUM> includes the input data length to the device <NUM> and the output data length from the device <NUM>. Further, the operational settings information <NUM> includes the identification information of the device <NUM>.

The generation unit <NUM> generates, on the basis of the operational settings information <NUM> corresponding to the device <NUM>, superordinate device settings information. Further, the generation unit <NUM> generates, on the basis of the operational settings information <NUM> corresponding to the device <NUM>, slave device settings information. Specifically, the superordinate device settings information is information for executing the IO memory allocation process based on the input data length and the output data length of the device <NUM>. For example, the superordinate device settings information includes information on the input data length and the output data length to be allocated in the IO memory of the superordinate device. Further, the slave device settings information is information for setting the input data length and the output data length for the device <NUM>. For example, the slave device settings information includes information on the input data length and the output data length to be allocated in the memory of the device management unit <NUM>. Further, the slave device settings information further includes the identification information of the device <NUM>. The identification information included in the slave device settings information is used in the collation process described later, which is executed in the device management unit <NUM>.

Further, the generation unit <NUM> causes each device to execute the settings process by transmitting the generated superordinate device settings information to the controller <NUM> and the communication coupler <NUM>, which are the superordinate devices of the unit management <NUM> to which the device <NUM> is connected, via the communication unit <NUM>. Further, the generation unit <NUM> causes the device to execute the process by transmitting the generated slave device settings information to the device management unit <NUM> to which the device <NUM> is connected via the communication unit <NUM>. Further, the slave device settings information is transmitted to the corresponding device management unit <NUM> via any of the controller <NUM> and the communication coupler <NUM>.

<FIG> is a flowchart showing an example of an operation of a settings information generation device <NUM> according to the present embodiment. When the operation of <FIG> is executed, the settings information generation device <NUM> stores information representing the network configuration related to the controller <NUM>, the communication coupler <NUM>, and the device management unit <NUM> included in the control system <NUM>. And, when the operation of <FIG> is executed, the control system <NUM> may be in a state in which some or all of the devices <NUM> to be connected are not connected.

In step S101, the selection unit <NUM> accepts an operation of selecting, from multiple candidates, the device <NUM> to be connected to the communication port of the device management unit <NUM> included in the control system <NUM>. The selection unit <NUM> selects the device <NUM> indicated by the selected operation. The step is executed for an unselected communication port in which the device <NUM> to be connected is not yet selected among the communication ports of each device management unit <NUM>. Moreover, the step may be executed on the selected communication port that the device <NUM> to be connected to has already selected. In this case, the device <NUM> is newly selected in place of the selected device <NUM> for the communication port.

In step S102, the control unit <NUM> determines whether or not to execute the settings process. For example, the control unit <NUM> may determine whether or not to execute the settings process according to the input operation of the user.

In the case of No in step S102, the settings information generation device <NUM> repeats the process of step S101. In the case of Yes in step S102, the process of the next step S103 is executed.

In step S103, the acquisition unit <NUM> acquires the operational settings information <NUM> corresponding to each selected device <NUM> from the storage unit <NUM>.

In step S104, the generation unit <NUM> generates, on the basis of each acquired operational settings information, superordinate device settings information.

In step S105, the generation unit <NUM> generates, on the basis of the acquired operational settings information, slave device settings information.

In step S106, the generation unit <NUM> transmits the generated superordinate device settings information to the controller <NUM> and the communication coupler <NUM>, and automatically executes the settings process. As the device to which the superordinate device settings information is transmitted, the superordinate device of the device management unit <NUM> to which the device <NUM> indicated by the superordinate device settings information is connected is determined based on the network configuration of the control system <NUM>.

In step S107, the generation unit <NUM> transmits the generated slave device settings information to the corresponding device management unit <NUM>, and automatically executes the settings process. As the device to which the slave device settings information is transmitted, the device management unit <NUM> to which the device <NUM> indicated by the slave device settings information is connected is determined.

The processes of steps S106 to S107 may be executed in response to the user's operation. For example, the processes of steps S106 to S107 are executed in response to the operation of instructing the batch automatic settings of the superordinate device settings information and the slave device settings information. Further, the process of step S106 may be executed in response to the operation of instructing the automatic settings of the superordinate device settings information, and the process of step S107 may be executed in response to the operation of instructing the automatic settings of the slave device settings information.

With the above, the settings information generation device <NUM> terminates the operation.

<FIG> is a diagram showing an example of a selection screen G1 displayed in step S101.

A region G101 is a region for displaying a list of communication ports of the target device management unit <NUM> among the device management units <NUM> included in the control system <NUM>. Here, communication ports <NUM> to <NUM> of the device management unit <NUM> are displayed for the device management unit <NUM> of the identification information "A" (hereinafter also referred to as device management unit A). For example, in response to an input operation for a selection button (not shown) for selecting any of the device management units <NUM> included in the control system <NUM>, a list of communication ports of the corresponding device management unit <NUM> may be displayed in the region G101.

In the example of <FIG>, the device <NUM> with identification information "<NUM>" (hereinafter, also referred to as device <NUM>) is selected for the communication port <NUM>. The communication ports <NUM> and <NUM> are unselected.

A region G102 is a region for displaying a list of vendors of the device <NUM> that may be included in the control system <NUM>. Each vendor indicated in the region G102 may be selected by an input operation.

A region G103 is a region for displaying a list of the devices <NUM> provided by the relevant vendor. In the region G103, a list of the corresponding devices <NUM> is displayed according to the vendor selection operation in the region G102. Each device <NUM> indicated in the region G103 may be selected in association with any of the communication ports indicated in the region G101 by an input operation. For example, the drag operation may be performed by the mouse from the region indicating any of the devices <NUM> in the region G103 to the region indicating any of the communication ports in the region G101. In this case, the selection unit <NUM> selects the corresponding device <NUM> for the corresponding communication port by the drag operation. Further, when the corresponding communication port is not selected in the region G101 (the port <NUM> or <NUM> in the example of <FIG>), the selection unit <NUM> displays the identification information of the selected device <NUM> in place of the information of "unselected". Further, when the corresponding communication port has been selected (the port <NUM> in the example of <FIG>), the selection unit <NUM> displays the identification information of the selected device <NUM> in place of the identification information of the selected device <NUM>.

A settings button G104 accepts an input operation for performing the determination process in step S102 shown in <FIG>. When the input operation for the settings button G104 is accepted, it is determined to be Yes in step S102, and steps S103 to S107 are executed. That is, the operational settings information <NUM> is acquired for the selected device <NUM> (the device <NUM> in this example) shown in the region G103, and the superordinate device settings information and the slave device settings information are generated. Then, in the controller <NUM> or the communication coupler <NUM>, the IO allocation process based on the input/output data length of the device <NUM> is executed on the basis of the superordinate device settings information. Further, in the device management unit A, the settings process of the input/output data length and the identification information of the device <NUM> is executed on the basis of the slave device settings information.

The display of the selection screen G1 may be used to terminate when the input operation for a cancel button G105 is accepted.

<FIG> is a diagram showing an example of the operational settings information <NUM> acquired from the storage unit <NUM> in step S103. Here, the case where the control system <NUM> is an IO-Link system will be described. In this case, the operational settings information <NUM> corresponding to the device <NUM> is provided by the vendor as an IODD (IO Device Description) file. <FIG> is a diagram showing an example of information contained in the IODD file. In the present embodiment, the IODD file corresponding to each device <NUM> is acquired in advance and stored in the storage unit <NUM>.

In the IODD file, the vendor ID indicates the vendor identification information of the device <NUM>. The device ID indicates the identification information of the device <NUM>. An IO-Link revision indicates revision of IO-Link that the device <NUM> corresponds to. The combination of vendor ID, device ID and IO-Link revision corresponds to an example of device identification information in the invention. The input data length indicates the data length that the device management unit <NUM> accepts as input from the device <NUM>. The output data length indicates the data length output by the device management unit <NUM> to the device <NUM>.

The superordinate device settings information is generated on the basis of this IODD file. For example, it is assumed that the corresponding device management unit A is connected to the controller <NUM> via the communication coupler <NUM> as the device management unit 50_3 shown in <FIG>. In this case, in the communication coupler <NUM>, a <NUM>-byte IO memory allocation process is performed, on the basis of the superordinate device settings information, so as to store the input data from the device <NUM>. Further, a <NUM>-byte IO memory allocation process is performed so as to store the output data to the device <NUM>.

Further, slave device settings information is generated on the basis of this IODD file. Then, in the device management unit <NUM> to which the device <NUM> indicated by the slave device settings information is connected, on the basis of the slave device settings information, <NUM> bytes are set as the input data length of the device <NUM> (the storage region of the memory is allocated). Moreover, <NUM> bytes are set as the output data length of the device <NUM>. Further, as the identification information of the device <NUM>, vendor ID "<NUM>", device ID "<NUM>", and IO-Link revision "<NUM>" are set.

Here, the slave device settings information is used to collate whether the device <NUM> actually connected to the device management unit <NUM> matches the device <NUM> selected by the settings information generation device <NUM>.

Specifically, the device management unit <NUM> compares the identification information acquired from the actually connected device <NUM> with the identification information of the device <NUM> indicated by the slave device settings information, and determines whether or not they match. If they match, the device management unit <NUM> determines that the actually connected device <NUM> is the correct (planned) device <NUM>, and if they do not match, it determines that it is not correct.

In this way, the settings information generation device <NUM> may not only automatically execute the settings process according to the device <NUM> in the device management unit <NUM>, but also determine whether or not the actually connected device <NUM> is correct. For example, when the control system <NUM> is an IO-Link system, the slave device settings information is used in the collation function of the IO-Link master as the device management unit <NUM>. Details of the IO-Link will be described below.

IO-Link is standardized in IEC61131-<NUM> under the name of "Single-drop digital communication interface for small sensors and actuators" (SDCI), and is a standardized technology for communication between a master (PLC) (for example, the controller <NUM> in the control system <NUM>) which is a control device and a device such as a sensor and an actuator (e.g. the device <NUM> in the control system <NUM>). IO-Link is a new point-to-point serial communication protocol used to communicate between a master (PLC) and a device such as a sensor and an actuator.

The IO-Link is a communication protocol (for example, a second mode communication protocol in the control system <NUM>) capable of exchanging <NUM>-byte (<NUM> bits) of data (two-way communication), unlike the conventional protocol (for example, the communication protocol of a first mode in the control system <NUM>) that may only transmit on/off signals (<NUM> bit) from the device to the master (PLC). By connecting the master (PLC) and the device such as sensor and actuator with IO-Link, a signal from the device that could only receive binarized data such as on/off information in the past may now be acquired as <NUM>-byte numerical data. So, for example, in the case of a photoelectric sensor, it is possible to acquire information such as the amount of light received, the detection margin, and the internal temperature, in addition to being useful for investigating the cause of defects, it is also possible to diagnose product life and change the threshold value according to aging deterioration.

By using IO-Link, for example, device settings and maintenance may be automated. Further, by using IO-Link, programming of the master (PLC) can be greatly simplified, and further, the cost of the wiring cable can be reduced. Examples of devices include photoelectric sensors and proximity switches.

The IO-Link system includes an IO-Link device (generally a sensor, actuator, or a combination thereof), a standard <NUM>-wire sensor/actuator cable, and an IO-Link master (such as the device management unit <NUM> in the control system <NUM>).

Here, the IO-Link master has one or multiple ports, and one IO-Link device may be connected to each port. The IO-Link master performs point-to-point communication with the IO-Link device. The IO-Link master may exchange not only conventional binarized data (<NUM>-bit data) such as on/off information but also information other than binarized data (data larger than <NUM> bit) such as on/off information such as device identification information, device communication properties, device parameters, and process/diagnostic data information, and the like with the IO-Link device.

The IO-Link device refers to a device capable of exchanging data larger than <NUM> bit with the IO-Link master (for example, the device <NUM> (C) in the control system <NUM>).

The IO-Link device may operate without an IO-Link master in a conventional digital exchange mode called Standard IO (SIO) (e.g. the first mode in control system <NUM>); that is, it may be operated by using a master that may receive only binarized data such as on/off information from the sensor. Similarly, the IO-Link master is a device that may receive only binarized data such as on/off information from the IO-Link master using SIO; for example, the device <NUM> in the control system <NUM> may be operated.

The IO-Link master port holds the configuration data. When a port is set to SIO mode, the IO-Link master operates the port in the same way as a conventional port (a port that may exchange only binarized data such as on/off information). If a port is set to communication mode (COM mode) (e.g. the second mode in the control system <NUM>), the IO-Link master is a device connected to that port (IO-Link device, e.g. the device in the control system <NUM>). For example, data larger than <NUM> bit may be exchanged with the device <NUM> (C)) in the control system <NUM>.

By using IO-Link, information other than on/off data (data larger than <NUM> bit) may be acquired from the device such as sensor and actuator (IO-Link devices). Specifically, device identification information (the vendor ID, the device ID, the revision, and a serial number) and the like may be acquired.

The IO-Link master has a collation function for collating the device to be connected with the device actually connected to the port for each port. The IO-Link master executes the collation process at the timing when the IO-Link communication is established. For example, when an IO-Link device is connected to a port, the IO-Link master acquires device identification information and device communication properties from the connected IO-Link device.

Further, the IO-Link master stores in advance configuration settings information including identification information of a device (IO-Link device) to be connected for each port.

The IO-Link master refers to the configuration settings information to acquire the identification information of the device (IO-Link device) to be connected to the port, and determines whether or not it matches the identification of the device actually connected to the port (IO-Link device).

For example, the IO-Link master determines, for each port, whether the "vendor ID, device ID, IO-Link revision, serial number" of the device to be connected and the "vendor ID, device ID, IO-Link revision, serial number" of the actually connected match. If the IO-Link master determines that they do not match (collation error), the IO-Link master stops the IO-Link communication.

Moreover, one of the following two patterns may be selected for the identification information used by the IO-Link master in the collation process. First, the IO-Link master may be made to perform collation process using the vendor ID, the device ID, and the IO-Link revision (simple collation function). Second, the IO-Link master may be made to perform collation process using the vendor ID, the device ID, the IO-Link revision, and the serial number (detailed collation function). Here, if the serial number is not referred to during the collation process, as long as the device (the device having the same vendor ID, device ID, and IO-Link revision with the registered device, excluding the serial number) has the same format as the registered device, the IO-link master determines that the collation is normal and may perform IO-Link communication with the exchanged device even if the serial numbers do not match.

In the present embodiment, it is described that multiple operational settings information <NUM> corresponding to each of the multiple candidate devices <NUM> is stored in advance in the storage unit <NUM>. Not limited thereto, the operational settings information <NUM> may be acquired from an external server as needed. In this case, for example, the storage unit <NUM> may store access information to an external server that provides downloadable operational settings information <NUM> for each vendor of the device <NUM> that may be multiple candidates. For example, the acquisition unit <NUM> may access the above-mentioned external server provided by the vendor of the device <NUM> selected by the selection unit <NUM> based on the access information, and download the operational settings information <NUM> of the device <NUM>.

Further, in the present embodiment, it is described that the superordinate device settings information and the slave device settings information are transmitted from the settings information generation device <NUM> to the controller <NUM>, the communication coupler <NUM>, and the device management unit <NUM> via the network <NUM>. Not limited thereto, the superordinate device settings information and the slave device settings information may be stored in a portable storage medium in the settings information generation device <NUM>. In this case, by reading the portable storage medium into the controller <NUM>, the communication coupler <NUM>, and the device management unit <NUM>, the settings process may be automatically performed in each device.

Further, in the present embodiment, the superordinate device settings information and the slave device settings information are described as including both the input data length and the output data length of the device <NUM>, but having either one will do.

A settings information generation device according to an aspect of the invention generates settings information of a superordinate device that communicates with a slave device including a communication port to which the device is connected, the settings information generation device including a selection unit for accepting a selection of the device to be connected from a user; an acquisition unit for acquiring operational settings information including an input/output data length of the selected device; and a generation unit for generating, on the basis of the operational settings information, superordinate device settings information that sets a storage region in the superordinate device in which the superordinate device stores data exchanged with the device via the slave device.

According to the above configuration, since the user may use the superordinate device settings information in the settings work for setting the storage region in the superordinate device, it is not necessary to manually input the data length information of the input from the device or the output to the device. As a result, there is an effect that the settings information generation device can reduce the settings steps related to the device in the superordinate device that communicates with the slave device having the communication port to which the device is connected.

In the settings information generation device according to an aspect of the invention, the generation unit generates, on the basis of the operational settings information, slave device settings information that sets a storage region in the slave device in which the slave device stores data exchanged with the device.

According to the above configuration, since the user may use the slave device settings information in the settings work for setting the storage region in the slave device, it is not necessary to manually input information such as the input data length from the device or the output data length to the device. As a result, there is an effect that the settings information generation device can further reduce the settings steps related to the device in the slave device having the communication port to which the device is connected.

In the settings information generation device according to an aspect of the invention, the selection unit presents multiple candidates of the device to a user, and accepts a selection of the device to be connected from the multiple candidates; the acquisition unit acquires the operational settings information including identification information of the selected device; and the generation unit generates slave device settings information set for the slave device; the slave device settings information includes the identification information of the selected device used to collate whether the device actually connected to the slave device matches the selected device.

According to the above configuration, there is an effect that not only is it possible to further reduce the steps for setting the device in the slave device having the communication port to which the device is connected, but it is also possible to have the slave device collate whether or not the device connected to the slave device is the one to be connected.

The settings information generation device according to an aspect of the invention includes a storage unit storing multiple operational settings information in advance for the multiple candidates of the device, in which the acquisition unit acquires the operational settings information for the selected device from the storage unit.

According to the above configuration, there is an effect that the settings steps for the device that may be multiple candidates can be quickly reduced.

In the settings information generation device according to an aspect of the invention, the acquisition unit acquires the operational settings information for the selected device from an external server.

According to the above configuration, there is an effect that the device that may be multiple candidates may be set based on the latest operational settings information.

In the settings information generation device according to an aspect of the invention, the device is an IO-Link (registered trademark) device, in which the slave device is an IO-Link master.

According to the above configuration, there is an effect that by using the settings information generation device, it is possible to reduce the settings steps in the superordinate device of the slave device capable of communicating with the device by IO-Link.

In the settings information generation device according to an aspect of the invention, the superordinate device is a PLC.

According to the above configuration, there is an effect that by using the settings information generation device, it is possible to reduce the settings steps in the superordinate device suitable for automatically controlling the device.

In the settings information generation device according to an aspect of the invention, the superordinate device is a communication coupler that communicates with a PLC via a network.

According to the above configuration, there is an effect that by using the settings information generation device, it is possible to reduce the settings steps when the slave device to which the device is connected is connected to the superordinate device via the communication coupler.

A settings information generation method generates settings information of a superordinate device that communicates with a slave device including a communication port to which the device is connected, the settings information generation method including: a selection step, accepting a selection of the device to be connected from a user; an acquisition step, acquiring an operational settings information including an input/output data length of the selected device; and a generation step, generating, on the basis of the operational settings information, superordinate device settings information that sets a storage region in the superordinate device in which the superordinate device stores data exchanged with the device via the slave device.

According to the above configuration, since the user may use the superordinate device settings information in the settings work for setting the storage region in the superordinate device, it is not necessary to manually input information such as the input data length from the device or the output data length to the device. As a result, the settings information generation device has an effect of reducing the settings steps related to the device in the superordinate device that communicates with the slave device having the communication port to which the device is connected.

A control block (particularly, the selection unit <NUM>, the acquisition unit <NUM>, and the generation unit <NUM>) of the settings information generation device <NUM> may be realized by a logic circuit (hardware) formed in an integrated circuit (IC chip) or the like, or may be realized by software.

In the latter case, the settings information generation device <NUM> includes a computer that executes instructions of a program that is software that realizes each function. The computer includes, for example, one or more processors and a computer-readable recording medium that stores the program. Then, in the computer, the processor reads and executes the program from the recording medium, thereby achieving the object of the invention. As the processor, for example, a CPU (Central Processing Unit) may be used. As the recording medium, a "non-transitory tangible medium", for example, a ROM (Read Only Memory) or the like, a tape, a disk, a card, a semiconductor memory, a programmable logic circuit, or the like may be used. Further, a RAM (Random Access Memory) for expanding the above program may be further provided. Further, the program may be supplied to the computer via an arbitrary transmission medium (communication network, broadcast wave, etc.) capable of transmitting the program. Moreover, one aspect of the invention may also be realized in the form of a data signal embedded in a carrier wave, in which the above program is embodied by electronic transmission.

Claim 1:
A settings information generation device (<NUM>), generating settings information of a superordinate device (<NUM>/<NUM>) that communicates with a slave device (<NUM>) comprising a communication port to which a device (<NUM>) is connected to the slave device (<NUM>), the settings information generation device (<NUM>) comprising:
a selection unit (<NUM>) for accepting a selection of the device (<NUM>) to be connected from a user;
an acquisition unit (<NUM>) for acquiring operational settings information (<NUM>) comprising an input/output data length of the selected device (<NUM>); and characterized in that the settings information generation device (<NUM>) further comprising:
a generation unit (<NUM>) for generating, on the basis of the input/output data length of the selected device (<NUM>) in the operational settings information (<NUM>), superordinate device settings information that is adapted to set a storage region in the superordinate device (<NUM>/<NUM>) in which the superordinate device (<NUM>/<NUM>) stores data exchanged with the device (<NUM>) via the slave device (<NUM>).