WO2019225364A1 - Dispositif de gestion de réseau, système pourvu d'un dispositif de gestion de réseau, procédé de gestion de réseau, programme de gestion et support d'enregistrement - Google Patents
Dispositif de gestion de réseau, système pourvu d'un dispositif de gestion de réseau, procédé de gestion de réseau, programme de gestion et support d'enregistrement Download PDFInfo
- Publication number
- WO2019225364A1 WO2019225364A1 PCT/JP2019/018850 JP2019018850W WO2019225364A1 WO 2019225364 A1 WO2019225364 A1 WO 2019225364A1 JP 2019018850 W JP2019018850 W JP 2019018850W WO 2019225364 A1 WO2019225364 A1 WO 2019225364A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- information
- slave
- connection
- address
- error
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/44—Star or tree networks
Definitions
- the present invention relates to a management device that manages a network including nodes such as a master device and a slave device, a system including the network management device, a network management method, and a management program.
- FA Vectory Automation
- the installation operation of the slave device is an operation of setting a node address that is an ID for identifying each slave device by connecting the slave devices with a communication cable after arranging the slave device beside each production facility. These operations are performed manually based on the blueprint of the network.
- Patent Document 1 discloses a technique for preventing duplication of identification information between controlled devices.
- slave devices are installed in the factory.
- the maximum number of slave devices to be installed is 512, and wiring errors and node address setting errors in the installation work of the slave devices are increasing.
- Responses to these mistakes are also made manually, but in addition to the increase in the scale of the network, the area in the factory where the slave devices are installed also covers a wide area, so identify the slave device where the error has occurred It was difficult. Even if a slave device in which a mistake has occurred can be identified, it takes a lot of time to investigate a correction method for the mistake, causing a delay in the start-up of production equipment.
- a management device is a management device that manages a network including a master device and a plurality of slave devices connected to the master device, and a configuration information acquisition unit that acquires configuration information of the network;
- a connection error detecting unit configured to detect an error related to the connection of the slave device based on the configuration information.
- the configuration information includes address information of each slave device, and the connection error detection unit detects an address setting error of the slave device based on the address information. .
- the address setting error supports an address allocated for the master device, an address is duplicated among a plurality of slave devices, and the master device supports It is preferable that an address outside the range is used.
- the management device further includes an address update unit that updates the address information of the slave device in which the address setting error is detected, using the update address information.
- the configuration information includes slave connection information of each slave device
- the connection error detection unit represents slave information indicating the slave connection information and unique information for each model of each slave device. Based on the above, it is preferable to detect an error in the wiring of the slave device.
- the wiring error is a connection between output ports or input ports of the slave device.
- the configuration information includes, for each of the slave devices, address information allocated to the slave device, profile information for identifying the model of the slave device, and a slave device of a connection destination Or the slave connection information including information specifying the address of the master device and information specifying the connection port, and the slave information identifies the model of the slave device for each of the slave devices.
- connection error detection unit displays profile information for identifying the model of the slave device together with information on an error related to the detected connection.
- the management device is a management device that manages an EtherCAT (registered trademark) network including a master device and a plurality of slave devices connected to the master device, and acquires configuration information of the network. Based on the configuration information acquisition unit, the configuration information, and slave information indicating unique information for each model of each slave device, as an error related to the connection of the slave device, an error in address setting of the slave device, A connection error detection unit that detects a wiring error of the slave device, and an address update unit that updates the address information of the slave device in which the address setting error is detected, using update address information.
- the configuration information includes address information assigned to each slave device.
- slave connection information including profile information for identifying the model of the slave device, information for specifying the address of the slave device or master device of the connection destination, and information for specifying the connection port
- the slave information includes, for each of the slave devices, profile information for identifying the model of the slave device, and port information including information on the number of ports and the port type held by the slave device, and the connection error
- the detection unit uses an address allocated for the master device as an address setting error of the slave device, and the address is duplicated among a plurality of slave devices. And an address outside the range supported by the master device is used.
- the system according to the present invention includes a master device, a plurality of slave devices connected to the master device, and a management device that manages a network including the master device and the plurality of slave devices.
- a management device that manages a network including the master device and the plurality of slave devices.
- a management method is a management method for managing a network including a master device and a plurality of slave devices connected to the master device, the configuration information obtaining step for obtaining the configuration information of the network, A connection error detecting step of detecting an error related to the connection of the slave device based on the configuration information.
- a management program for causing a computer to function as the management device the management program for causing the computer to function as the configuration information acquisition unit and the connection error detection unit, and a computer readable recording of the management program
- Such recording media are also within the technical scope of the present invention.
- FIG. 7 is a diagram illustrating an example of configuration information acquired from a master device and slave information acquired from each slave device in the network configuration illustrated in FIG. 6. It is a flowchart which shows the flow of the process in the management method which concerns on one Embodiment of this invention. It is a flowchart which shows the flow of the process in the management method which concerns on one Embodiment of this invention.
- FIG. 1 is a block diagram showing a schematic configuration of an industrial network system 100 according to an embodiment of the present invention.
- the industrial network system 100 includes a master device 1, a network including a slave device 2 connected to the master device 1, and a management device 3 connected to the master device 1.
- the master device 1 and the slave device 2 are connected by a cable 4 compatible with EtherCAT communication, and the slave devices 2 are also connected by a cable 4 compatible with EtherCAT communication.
- the master device 1 and the management device 3 are connected by wired or wireless Ethernet (registered trademark) communication or USB communication.
- wired or wireless Ethernet registered trademark
- the master device 1 is a device that centrally manages the slave devices 2, and is composed of, for example, a PLC (Programmable Logic Controller).
- the master device 1 controls the slave device 2 by transmitting a control command for performing sequence control to the slave device 2, and monitors the status of the slave device 2 by receiving various data from the slave device 2.
- the slave device 2 is a device that collects and controls data of the production facility, and performs a control operation of the production facility according to a control command from the master device 1 and rewrite and return processing of the received control command.
- the slave device 2 includes a slave terminal, NX unit, CJ unit, IO-Link device, power supply unit, motor unit, counter unit, image unit, communication unit, I / O unit, and the like.
- the slave device 2 is appropriately connected to a production facility by wire or wireless.
- Production equipment includes input devices such as sensors, push buttons, limit switches, and output devices such as lamps.
- the number and topology of the slave devices 2 connectable to the master device 1 are not particularly limited.
- a maximum of 512 slave devices 2 can be connected to one master device 1, and can be connected in series, ring shape, tree shape or star shape depending on the cooperation between the slave devices 2 and the convenience of wiring. Any topology can be applied.
- a hub device may be included as a node.
- FIG. 2 is a block diagram showing a schematic configuration of the management apparatus 3 according to an embodiment of the present invention.
- the management device 3 is a computer that manages the network of the master device 1 and the slave device 2, and can be configured by, for example, a general-purpose personal computer.
- the management device 3 includes, for example, a CPU (Central Processing Unit), a main storage device (memory), an auxiliary storage device (hard disk, SSD, etc.), a display device, and an input device (keyboard, mouse, etc.) as a hardware configuration. Yes.
- the management device 3 includes a communication unit 31, a troubleshooting control unit 32, a network management unit 33, a network management storage unit 35, and an auxiliary storage unit 36 as functional blocks.
- the communication unit 31, the troubleshooting control unit 32, and the network management unit 33 are realized by a management program (not shown) stored in the auxiliary storage device being read into the main storage device and executed by the CPU.
- the management program may be recorded on a non-transitory computer-readable recording medium such as a CD-ROM, and the management program may be installed in the management apparatus 3 by causing the management apparatus 3 to read the recording medium. Good.
- the management program code may be downloaded to the management apparatus 3 via a communication network such as the Internet.
- the storage unit 35 can be set as a main storage device.
- the auxiliary storage unit 36 can be set as an auxiliary storage device.
- the communication unit 31 is a communication unit for the management device 3 to communicate with the master device 1.
- the communication unit 31 has a function of switching a communication protocol according to the master device 1.
- the troubleshooting control unit 32 has a function of supporting the resolution of various network problems including the master device 1 and the slave device 2.
- the network management unit 33 has a function of supporting network state management by the user.
- the network management unit 33 includes a configuration information acquisition unit 331, a connection error detection unit 332, an address update unit 333, and a network configuration diagram display unit 334.
- slave information D2 in which unique information for each model of each slave apparatus 2 constituting the industrial network system 100 is described is stored in advance.
- the slave information D2 is a file created in advance by a vendor of each slave device 2 in a format such as XML format.
- the slave information D2 includes profile information and port information.
- the profile information is information for identifying the model of the slave device 2 and includes, for example, a product code, a vendor ID, a revision number, and the like of the slave device.
- the port information is information related to the ports held by the slave device 2, and includes information such as the number of ports and port types, for example.
- the configuration information acquisition unit 331 is a functional block that acquires network configuration information (configuration information) of an actual machine.
- the master device 1 performs network scan processing to collect information on each slave device 2 and generate configuration information.
- the configuration information acquisition unit 331 receives this configuration information from the master device 1 and reads it into the storage unit 35 as the configuration information D1 shown in FIG.
- the profile information is information for identifying the model of the slave device 2 and includes, for example, a product code, a vendor ID, a revision number, and the like of the slave device.
- the slave connection information is information for understanding the connection configuration (topology) of the slave device, and includes, for example, information for specifying the connection destination device and port of the slave device.
- the address information is information indicating the value of the node address assigned to the slave device.
- the network scan process is executed by the following four steps, for example.
- an EtherCAT standard network will be described as an example.
- the master device 1 determines the number of slave devices 2 (number of nodes) connected to the master device 1. In order to determine the number of nodes, the master device 1 issues a broadcast command (BRD) to the network.
- BTD broadcast command
- the number of broadcast command responses corresponds to the number of nodes connected to the master device 1.
- EtherCAT standard stipulates that all nodes (all EtherCAT slaves) existing in the network respond to a broadcast command.
- the master device 1 acquires node address information and communication port information established in each node from each node on the network. In order to acquire information, the master device 1 issues an APRD (auto-increment-physical-read) command to each node.
- APRD auto-increment-physical-read
- the APRD command is a command used for reading a register in the EtherCAT standard. Reading is performed by specifying a node by a position address (an address indicating the number of connected devices counted from the master device 1).
- the master device 1 creates a network topology based on the communication port information acquired in the second step and the rules of the packet circulation order.
- the EtherCAT standard specifies that the IN communication port of a node is the 0th port. Further, it is specified that the order in which the packet circulates the communication port is the order of the 0th port, the 3rd port, the 1st port and the 2nd port.
- the master device 1 acquires information for specifying the model of the node from each node on the network. In order to acquire information, the master device 1 issues the above APRD command to each node.
- the EtherCAT standard stipulates that a node holds a vendor ID, a product code, and a revision code on a register as information for specifying a model.
- the network scan process is performed by the above four steps, and the configuration information D1 is generated.
- the connection error detection unit 332 is a functional block that detects an error related to the connection of each slave device 2 based on the configuration information D1.
- the connection error detection unit 332 detects an error in wiring between slave devices and an error in address setting of the slave devices as errors related to the connection.
- the order of detecting the wiring error and the address setting error is not limited, but in this embodiment, the wiring error is detected first and then the address setting error is detected.
- the connection error detection unit 332 detects both a wiring error and an address setting error, but may detect either a wiring error or an address setting error.
- the connection error detection unit 332 detects an address setting error of the slave device 2 based on the address information of each slave device 2 included in the configuration information D1.
- the connection error detecting unit 332 displays profile information for identifying the model of the slave device 2 together with the detected address setting error information as illustrated in FIG. To do.
- an address setting error is detected for the three slave devices 2 displayed together with the icon E1.
- the address values “0”, “5”, “5”, which are the address values set in error, and the message 41 indicating the content of the address setting error are stored in the slave device 2. Displayed with profile information.
- the address setting error includes various modes. For example, when the address (reserved address) allocated for the master device 1 is used for the slave device 2, the connection error detection unit 332 determines that the address setting is incorrect. For example, when the address is set redundantly among the plurality of slave devices 2, the connection error detection unit 332 determines that the address setting is incorrect. For example, when an address having a value outside the range supported by the master device 1 is set in the slave device 2, the connection error detection unit 332 determines that an address setting error has occurred.
- the connection error detection unit 332 Based on the slave connection information of each slave device 2 included in the configuration information D1 and the unique information for each model of each slave device 2 included in the slave information D2, the connection error detection unit 332 An error in the wiring of the device 2 is detected. When a wiring error is detected, the connection error detection unit 332 displays profile information for identifying the model of the slave device 2 together with information on the detected wiring error, for example, as illustrated in FIG. In the illustrated example, a wiring error is detected for one slave device 2 displayed with the icon E1. As information regarding the wiring error, an address value “2” that is the address value of the slave device 2 that has been incorrectly wired, and a message 43 indicating the content of the wiring error are displayed together with the profile information of the slave device 2. Yes.
- connection error detection unit 332 determines that there is a wiring error. More specific procedures for detecting wiring errors will be described later with reference to FIGS.
- the slave device 2 may be temporarily removed (detached) from the network for reasons such as maintenance, but can rejoin the network after returning from maintenance.
- a disconnection due to temporary disconnection can be processed without determining that it is a wiring error.
- Information of the slave device 2 to leave can be left in the configuration information D1 as it is still connected to the network.
- the address update unit 333 is a functional block that updates the address information using the update address information for the slave device 2 in which an address setting error is detected.
- the address updating unit 333 displays the address writing screen illustrated in FIG.
- the address information for update is input by the user via an input device, for example.
- an input device for example.
- the user selects an address value indicated by reference numeral 45, the user can input an update address value.
- the address value of the slave device 2 whose address value is currently set to “0” is changed to the address value “3”.
- the address update unit 333 updates the address value.
- the update of the address value refers to updating the address information included in the configuration information D1 for the slave device 2 in which an address setting error is detected, and is connected to the network with the content of the updated configuration information D1.
- the information of the slave device 2 is updated.
- the update of the address value for the slave device 2 is performed according to the following procedure.
- a node address write request of the slave device 2 to be updated is issued from the address update unit 333 of the management device 3 to the master device 1.
- the node address write request can be issued via any communication protocol.
- the master device 1 that has received the node address write request issues a node address write request to the slave device 2 to be updated.
- the slave device 2 that has received the node address write request writes a new node address in a prescribed register of the slave device 2.
- the network configuration diagram display unit 334 is a functional block that displays a network configuration diagram showing the connection relationship of nodes.
- the network configuration diagram display unit 334 refers to the configuration information D1 stored in the storage unit 35 and graphically displays the network configuration diagram 47 illustrated in the address writing screen of FIG.
- nodes included in the network are indicated by icons and displayed in a tree form. Further, in the vicinity of each icon, a node address and a model name of the node are displayed. Note that the specific display mode of the network configuration diagram 47 is not limited to this, as long as the user can intuitively grasp the network configuration.
- connection error detection unit 332 detects a wiring error
- FIG. 6 is a block diagram showing an example of a network configuration during installation work.
- five slave devices 2 (2a to 2e) are connected to the master device 1 and below, and miswiring occurs between the slave device 2b and the slave device 2c. The ports are connected incorrectly.
- FIG. 7 is a diagram illustrating an example of configuration information acquired from the master device and slave information acquired from each slave device in the network configuration illustrated in FIG. 6.
- the slave information D2a is profile information and port information of the slave device 2a.
- the slave device 2a determines that the master device 1 and the management device 3 are connected to the network by the address information, profile information, and slave connection information indicated in the configuration information D1a by the network scan process described above. Has been.
- the slave information D2b to D2e is profile information and port information of the slave devices 2b to 2e, respectively.
- the slave devices 2b to 2e are determined to be connected to the network from the master device 1 and the management device 3 with the contents shown in the configuration information D1b to D1e, respectively.
- ADR is address information set in the slave device 2.
- PC is the product code of the slave device 2
- Ver is the revision number. These product codes and revision numbers correspond to profile information.
- slave connection information address information for specifying a connection destination port and node is shown.
- PC is the product code of the slave device 2
- Ver is the revision number. These product codes and revision numbers correspond to profile information.
- port information information regarding the number of ports and the port type held by the slave device 2 is shown.
- connection error detection unit 332 performs wiring of the slave device 2 based on the slave connection information in the configuration information D1 and the port information in the slave information D2 that are associated one-to-one with the profile information in accordance with the following procedure. Detect errors. In FIG. 7, portions of the configuration information D1 and the slave information D2 that should be noted are underlined.
- connection error detection unit 332 repeatedly performs the following determination in the order of slave information D2a to D2e corresponding to the slave devices 2a to 2e, for example.
- the connection error detection unit 332 confirms the port number “Port1” of the port whose port type is set to “output port (Output)” in the port information of the slave information D2b for the slave device 2b.
- connection error detection unit 332 confirms the corresponding port number “Port1” in the configuration information D1b associated one-to-one with the profile information, and confirms the set connection destination address “ADR ⁇ 3 ”.
- connection error detection unit 332 refers to the configuration information D1c of the slave device 2c designated by the connection destination address “ADR 3”, and the port number “Port1” of the port in which the connection source address “ADR 2” is set. Confirm.
- the connection error detection unit 332 confirms the port type of the corresponding port number “Port1” of the corresponding slave information D2c that is associated one-to-one with the profile information. If the confirmed port type is set to “output port (Output)”, it is determined that the wiring is incorrect because it is a connection between the output ports. On the other hand, if the confirmed port type is set to “input port”, it is determined that the connection is normal because the output port is connected to the input port. In this example, since the confirmed port type is set to “output port (Output)”, the connection error detection unit 332 connects the slave device 2b and the slave device 2c with incorrect wiring between the output ports. Judge that there is.
- connection error detection unit 332 repeatedly performs the above determination in the order of the slave information D2a to D2e.
- the connection error detection unit 332 can interrupt the process at the time when even one erroneous wiring is determined.
- the port number of the port whose port type is set to “Input Port” in the port information of the slave device 2 is selected. Confirm. Thereafter, as in the case of detecting the erroneous wiring between the output ports described above, the consistency of the connection relation is traced and the erroneous wiring is determined.
- FIGS. 8 to 9 are flowcharts showing the flow of processing in the management method for managing the network including the master device 1 and the slave device 2. In the figure, processing procedures in the management device 3 and the master device 1 are shown.
- the user starts a management program in the management device 3 (S1), and when the user presses an online button (not shown) on the management program screen, the communication unit 31 starts communication with the master device 1 (S2). ).
- the troubleshooting control unit 32 is activated (S3).
- the configuration information acquisition unit 331 instructs the master device 1 to transmit configuration information (S4).
- the master device 1 collects information of each slave device 2 by performing a network scan process (S21), and stores the configuration information in its own device (S22).
- the master device 1 transmits the configuration information stored in its own device to the management device 3 (S23).
- the configuration information acquisition unit 331 acquires the configuration information D1 and stores it in the storage unit 35 (S5).
- connection error detection unit 332 detects an error related to the connection of each slave device 2.
- connection error detection unit 332 detects a wiring error of the slave device 2 (S6).
- the connection error detection unit 332 When a wiring error is detected (NO in S6), the connection error detection unit 332 includes profile information for identifying the model of the slave device 2 along with the detected wiring error information as illustrated in FIG. Display (S7). By displaying the icon E1, the user can easily grasp that there is an error in the wiring in the slave device 2 having the address value “2”. Also, the profile information displayed together allows the user to obtain information for specifying the model of the slave device 2 having an error in wiring.
- the management device 3 instructs the master device 1 to transmit the configuration information again (S4).
- the updated configuration information D1 is acquired (S5).
- the management device 3 detects an error related to the connection of each slave device 2. That is, the management device 3 repeatedly executes the processing from step S4 to S6 until all the wiring errors of the slave device 2 are resolved.
- connection error detection unit 332 continues to detect an error in the address setting of the slave device 2 (S8).
- connection error detecting unit 332 identifies the model of the slave device 2 together with the detected address setting error information as illustrated in FIG. Information is displayed (S9).
- the icon E1 By displaying the icon E1, the user can easily grasp that the address values “0”, “5”, and “5” set in the slave device 2 are incorrect. Also, the profile information displayed together allows the user to obtain information for specifying the model of the slave device 2 in which an incorrect address value is set.
- the address updating unit 333 displays the address writing screen illustrated in FIG. 5 (S10).
- the management device 3 instructs the master device 1 to transmit the configuration information again (S4), and acquires the updated configuration information D1 from the master device 1 (S5).
- the management device 3 detects an error related to the connection of each slave device 2. That is, the management device 3 repeatedly executes the processes from step S4 to S8 until all the wiring errors and address setting errors of the slave device 2 are resolved.
- the industrial network system 100 detects no wiring error or address setting error in the slave device 2, and the management device 3 ends a series of detection processes. To do.
- the network management device 3 that supports the installation work of the slave device 2 can be provided.
- the management device 3 can detect a wiring error of the slave device 2 and an address setting error of the slave device 2 as errors related to the connection of the slave device 2.
- the management device 3 can display profile information for identifying the model of the slave device 2 along with information indicating the content of the detected error.
- the user identifies the slave device 2 in which a wiring error or a node address setting error has occurred for each cause of the mistake in the installation work of the slave device when starting up the production equipment, and the slave device 2 It is possible to grasp the information. Thereby, the start-up of production equipment can be speeded up.
- the address value is updated in software via the address writing screen in step S10, but the present invention is not limited to this.
- the incorrect address value may be corrected by the user directly switching the hardware switch of the slave device 2 in which the incorrect address value is set.
- Master device 2 (2a to 2e) Slave device 3 Management device 4 Cable 31 Communication unit 32 Troubleshooting control unit 33 Network management unit 331 Configuration information acquisition unit 332 Detection unit 333 Address update unit 334 Network configuration diagram display unit 35 Storage unit 36 Auxiliary storage unit 100 Industrial network system D1 (D1a to D1e) Configuration information D2 (D2a to D2e) Slave information
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Small-Scale Networks (AREA)
Abstract
La présente invention concerne un dispositif de gestion de réseau qui aide le fonctionnement d'installation de dispositifs esclaves. Un dispositif de gestion (3) gère un réseau comprenant un dispositif maître (1) et une pluralité de dispositifs esclaves connectés au dispositif maître (1). Le dispositif de gestion (3) est pourvu d'une unité d'acquisition d'informations de configuration (331) qui acquiert des informations de configuration du réseau, et d'une unité de détection d'erreur de connexion (332) qui, sur la base des informations de configuration, détecte une erreur concernant la connexion des dispositifs esclaves.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2018099756 | 2018-05-24 | ||
JP2018-099756 | 2018-05-24 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2019225364A1 true WO2019225364A1 (fr) | 2019-11-28 |
Family
ID=68616053
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2019/018850 WO2019225364A1 (fr) | 2018-05-24 | 2019-05-13 | Dispositif de gestion de réseau, système pourvu d'un dispositif de gestion de réseau, procédé de gestion de réseau, programme de gestion et support d'enregistrement |
Country Status (1)
Country | Link |
---|---|
WO (1) | WO2019225364A1 (fr) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2023007914A1 (fr) * | 2021-07-30 | 2023-02-02 | 住友電気工業株式会社 | Dispositif de gestion, procédé d'inspection, et programme d'inspection |
CN116938691A (zh) * | 2023-09-19 | 2023-10-24 | 钛玛科(北京)工业科技有限公司 | 一种设备系统网络中的主机搭建方法及系统 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH0621949A (ja) * | 1992-07-03 | 1994-01-28 | Toshiba Corp | データ伝送装置 |
JPH07182273A (ja) * | 1993-10-28 | 1995-07-21 | Internatl Business Mach Corp <Ibm> | ネットワーク・システムおよびアダプタ |
JP2018011147A (ja) * | 2016-07-12 | 2018-01-18 | オムロン株式会社 | 情報処理装置、情報処理プログラムおよび情報処理方法 |
JP2018019199A (ja) * | 2016-07-27 | 2018-02-01 | 株式会社日立ハイテクノロジーズ | 分散制御装置及び分散制御システム |
-
2019
- 2019-05-13 WO PCT/JP2019/018850 patent/WO2019225364A1/fr active Application Filing
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH0621949A (ja) * | 1992-07-03 | 1994-01-28 | Toshiba Corp | データ伝送装置 |
JPH07182273A (ja) * | 1993-10-28 | 1995-07-21 | Internatl Business Mach Corp <Ibm> | ネットワーク・システムおよびアダプタ |
JP2018011147A (ja) * | 2016-07-12 | 2018-01-18 | オムロン株式会社 | 情報処理装置、情報処理プログラムおよび情報処理方法 |
JP2018019199A (ja) * | 2016-07-27 | 2018-02-01 | 株式会社日立ハイテクノロジーズ | 分散制御装置及び分散制御システム |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2023007914A1 (fr) * | 2021-07-30 | 2023-02-02 | 住友電気工業株式会社 | Dispositif de gestion, procédé d'inspection, et programme d'inspection |
JP2023020328A (ja) * | 2021-07-30 | 2023-02-09 | 住友電気工業株式会社 | 管理装置、検査方法および検査プログラム |
JP7431199B2 (ja) | 2021-07-30 | 2024-02-14 | 住友電気工業株式会社 | 管理装置、検査方法および検査プログラム |
CN116938691A (zh) * | 2023-09-19 | 2023-10-24 | 钛玛科(北京)工业科技有限公司 | 一种设备系统网络中的主机搭建方法及系统 |
CN116938691B (zh) * | 2023-09-19 | 2023-12-26 | 钛玛科(北京)工业科技有限公司 | 一种设备系统网络中的主机搭建方法及系统 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8966028B2 (en) | Virtual placeholder configuration for distributed input/output modules | |
JP2002268707A (ja) | コントローラ及びツール並びにそれらにより構成されるシステム | |
JP6874438B2 (ja) | スレーブ装置、スレーブ装置の制御方法、情報処理プログラム、および記録媒体 | |
WO2020195503A1 (fr) | Dispositif de gestion de réseau, procédé de gestion, programme de gestion, et support d'enregistrement | |
WO2019225364A1 (fr) | Dispositif de gestion de réseau, système pourvu d'un dispositif de gestion de réseau, procédé de gestion de réseau, programme de gestion et support d'enregistrement | |
EP3561623A1 (fr) | Dispositif de gestion de réseau, procédé de gestion, programme de gestion et support d'enregistrement | |
JP2017163508A (ja) | マスタースレーブ制御システム、マスタースレーブ制御システムの制御方法、情報処理プログラム、および記録媒体 | |
JP3757669B2 (ja) | 分散システムの設定方法 | |
JP2017167593A (ja) | 中継装置、中継装置の制御方法、制御プログラム、および記録媒体 | |
US11165745B2 (en) | Control system, controller, and control method | |
JP2010287034A (ja) | 外部機器とPLCとのModbusプロトコル通信アドレス表示方式 | |
JP2012150795A (ja) | 分散システムにおけるフィールド装置の一体化 | |
JP2008181572A (ja) | Plcシステム | |
JPWO2016157477A1 (ja) | 管理システム | |
WO2018008094A1 (fr) | Dispositif de modification de paramètres pour dispositif de commande d'équipement industriel, système de commande d'équipement industriel, procédé de fabrication de système de commande d'équipement industriel, et programme | |
CN113545013B (zh) | 网络管理装置、管理方法以及记录介质 | |
US20190303319A1 (en) | Support apparatus, non-transitory computer-readable recording medium and setting method | |
JP2003131709A (ja) | 制御表示装置、制御プログラムおよびそれを記録した記録媒体 | |
JP3345361B2 (ja) | 制御装置 | |
JP6723493B1 (ja) | 生産支援装置、生産システム及びプログラム | |
JP2019040550A (ja) | 制御プログラム変換装置および方法 | |
JP5720330B2 (ja) | 制御システム、操作端末およびプログラム | |
JP2024053927A (ja) | 照明制御システム | |
CN110703716A (zh) | 一种应用于自动化控制系统下的多设备通信方法 | |
JP2021027449A (ja) | ネットワークシステム、情報処理装置、および情報処理方法 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 19807438 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 19807438 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: JP |