WO2016157477A1 - Système de gestion - Google Patents

Système de gestion Download PDF

Info

Publication number
WO2016157477A1
WO2016157477A1 PCT/JP2015/060386 JP2015060386W WO2016157477A1 WO 2016157477 A1 WO2016157477 A1 WO 2016157477A1 JP 2015060386 W JP2015060386 W JP 2015060386W WO 2016157477 A1 WO2016157477 A1 WO 2016157477A1
Authority
WO
WIPO (PCT)
Prior art keywords
slave device
information
slave
management
communication
Prior art date
Application number
PCT/JP2015/060386
Other languages
English (en)
Japanese (ja)
Inventor
豊 川口
Original Assignee
三菱電機株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 三菱電機株式会社 filed Critical 三菱電機株式会社
Priority to KR1020177031475A priority Critical patent/KR101849512B1/ko
Priority to JP2016559381A priority patent/JP6177455B2/ja
Priority to CN201580078436.5A priority patent/CN107430391B/zh
Priority to PCT/JP2015/060386 priority patent/WO2016157477A1/fr
Publication of WO2016157477A1 publication Critical patent/WO2016157477A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B19/00—Programme-control systems
    • G05B19/02—Programme-control systems electric
    • G05B19/04—Programme control other than numerical control, i.e. in sequence controllers or logic controllers
    • G05B19/042—Programme control other than numerical control, i.e. in sequence controllers or logic controllers using digital processors

Definitions

  • the present invention relates to a management system that manages information on slave devices connected to a network.
  • a system is known that is configured by a sensor network in which sensors are connected and a monitoring device including a PLC (Programmable Logic Controller) performs sensor monitoring and control of a control target device.
  • PLC Programmable Logic Controller
  • a system in which sensor configuration management and device operation settings are performed by an engineering tool in a sensor network is also known.
  • the above-described system there is a system that performs setting or monitoring of a slave device via a network from a control device including a PLC in a production line.
  • the conventional engineering tool uses the slave device information data stored in the engineering tool for each slave device connected to the network to recognize the slave devices connected to the network, and Monitoring, configuration management and device operation settings were performed.
  • the device operation setting of the slave device installed on the production line is performed, if the engineering tool does not hold the slave device information of the slave device, the version upgrade work of the engineering tool or the slave device information Import work was necessary.
  • a controller or a control device that is a PLC inquires of each sensor about a sensor identifier. Subsequently, the control device requests the sensor determined to have the interface program based on the sensor identifier to upload the interface program stored in the sensor. Subsequently, the control device transmits and receives data necessary for normal sensing processing to the corresponding sensor using the interface program uploaded from the sensor.
  • the engineering tool may manage each slave device by collecting device information from each slave device via the control device.
  • the device information system of each manufacturer may be used if the manufacturers are different.
  • different manufacturers handle different protocols for different manufacturers, it is necessary to add device information to the engineering tool.
  • an error which is one piece of information regarding the state of the device, is displayed on the engineering tool or other devices, the error may not be displayed.
  • the present invention has been made in view of the above, and an object of the present invention is to obtain a management system capable of displaying information on the state of a device without depending on the type of device manufacturer.
  • a management system uses a control device that communicates using the first communication method and a second communication method different from the first communication method.
  • the first slave device communicating with the control device using the first communication method and the first slave device communicating with the first slave device using the second communication method.
  • First communication device that relays to the slave device, and first slave device information that is information of the first slave device from the first slave device via the control device and the first communication device And a management device that acquires and stores the information.
  • the present invention has an effect that a management system capable of displaying information related to the state of the device without depending on the manufacturer type of the device can be obtained.
  • FIG. Block diagram of a first slave device according to the first embodiment Block diagram of a first slave device according to the first embodiment Figure showing an example of an error code table showing the correspondence between error codes and error contents
  • the figure which shows the state in which the error code was displayed on the display apparatus 2M The flowchart which shows the operation
  • FIG. 1 is a diagram illustrating a management system according to the first embodiment.
  • the management system 1 according to the first embodiment communicates with the control device 3, the slave devices 51a, 51b, 51c, 51d, 51e, and 51f, and the control device 3 and the slave devices 51a, 51b, 51c, 51d, 51e, and 51f.
  • the communication device 4F that relays between the control device 3 and the slave devices 51a, 51b, 51c, 51d, 51e, and 51f, and the slave devices 51a, 51b, 51c, 51d, 51e, and 51f via the control device 3
  • a management device 2 that acquires the slave device information IF, which is The slave device information IF is stored in at least one of the slave devices 51a, 51b, 51c, 51d, 51e, 51f and the communication device 4F.
  • the control device 3 communicates using the first communication method.
  • the slave devices 51a, 51b, 51c, 51d, 51e, and 51f communicate using a second communication method that is different from the first communication method.
  • the communication device 4F communicates with the control device 3 using the first communication method, communicates with the slave devices 51a, 51b, 51c, 51d, 51e, and 51f using the second communication method, and communicates with the control device 3 and the first device.
  • the management apparatus 2 acquires and stores slave device information IF from the slave devices 51a, 51b, 51c, 51d, 51e, and 51f via the control device 3 and the communication device 4F.
  • the slave devices 51a, 51b, 51c, 51d, 51e, and 51f are appropriately referred to as first slave device slave devices 51a, 51b, 51c, 51d, 51e, and 51f, and the communication device 4F is appropriately connected to the first communication. This is referred to as device 4F. Further, when the first slave devices 51a, 51b, 51c, 51d, 51e, and 51f are not distinguished, they are referred to as the first slave device 51.
  • the slave device information IF is appropriately referred to as first device information IFf.
  • the management system 1 includes a management device 2, a control device 3, a first communication device 4F, a first slave device 51, a communication line 60, a first communication line 61, and a second communication line 62.
  • a network 11 is formed.
  • the management device 2 and the control device 3 are connected by a communication line 60.
  • the control device 3 and the first communication device 4F are connected by a first communication line 61.
  • the first communication device 4F and the first slave devices 51a, 51b, 51c, 51d, 51e, 51f are connected by a second communication line 62.
  • the first communication line 61 is a communication line used for communication using the first communication method.
  • the second communication line 62 is a communication line used for communication using a second communication method different from the first communication method.
  • CC-Link IE Field is used for the first communication line 61
  • AnyWireASLINK is used for the second communication line 62.
  • the first communication method is a communication method compliant with CC-Link IE Field
  • the second communication method is a communication method compliant with AnyWireASLINK.
  • the first communication line 61 is not limited to CC-Link IE Field
  • the second communication line 62 is not limited to AnyWireASLINK. For this reason, the first communication method is not limited to the CC-Link IE Field communication method, and the second communication method is not limited to the AnyWireASLINK communication method.
  • the communication line 60 uses Ethernet (registered trademark).
  • Ethernet registered trademark
  • the communication system used between the management apparatus 2 and the control apparatus 3 is a communication system based on Ethernet.
  • the communication method used between the management device 2 and the control device 3 is not limited to a communication method compliant with Ethernet.
  • the communication method used between the management device 2 and the control device 3 is different from the first communication method and the second communication method.
  • the different communication methods refer to the case where at least one of the physical standard and the communication protocol is different.
  • the management system 1 manages the first slave device 51.
  • Management of the first slave device 51 includes setting a control parameter or specification of the first slave device 51 in the control device 3.
  • the management of the first slave device 51 is performed when a new first slave device 51 is connected to the network 11 of the management system 1 or when the connected first slave device 51 is updated.
  • the setting of the device configuration state of the first slave device 51 in the control device 3 is also included.
  • FIG. 2 is a functional block diagram of the management apparatus according to the first embodiment.
  • FIG. 3 is a diagram illustrating a device configuration of the management device according to the first embodiment.
  • the management device 2 includes a processing unit 20C that processes information, a storage unit 20M that stores information, a communication unit 20T that communicates with devices outside the management device 2, and a display device 2M that displays information.
  • the device external to the management device 2 is the control device 3.
  • the processing unit 20C includes a processor such as a CPU (Central Processing Unit) and a primary storage device that can be directly accessed by the processor.
  • the primary storage device includes a register, a cache memory, and a RAM (Random Access Memory).
  • the storage unit 20M includes a secondary storage device that cannot be directly accessed by the processor.
  • the storage unit 20M is exemplified by ROM (Read Only Memory), SSD (Solid State Drive) or HDD (Hard Disk Drive).
  • the processing unit 20C executes the program stored in the secondary storage device while using the RAM as a work area.
  • Examples of the program stored in the secondary storage device include BIOS (Basic Input Output System) or UEFI (Unified Extensible Firmware Interface).
  • Examples of the computer program stored in the storage unit 20M include a computer program for realizing the management system 1, an operating system program, and an engineering tool program.
  • the communication unit 20T is a communication interface for the management apparatus 2 to communicate with the control device 3 via the communication line 60.
  • the communication unit 20T can be realized by a NIC (Network Interface Card) and a LAN (Local Area Network) driver installed in the personal computer.
  • the management device 2 is a personal computer, a tablet computer, or a smartphone.
  • the management device 2 only needs to include the processing unit 20C, the storage unit 20M, and the communication unit 20T, and is not limited to those described above.
  • the processing unit 20C includes a management unit 21 and an information request unit 22.
  • the management unit 21 acquires the slave device information IF corresponding to each slave device 5, stores it in the storage unit 20M, and manages it.
  • the management unit 21 stores the type, function, and specification of the slave device 5 connected to the second communication line 62 in the form of a data table, and manages the first slave device 51 based on the data table.
  • the management unit 21 uses the first slave device information IFf corresponding to each slave device 5 to set the control parameter or specification of the first slave device 51 in the control device 3, so that the first slave device 51 is managed.
  • the management unit 21 acquires slave device information from the slave device 5 via the second communication line 62, the first communication device 4F, the first communication line 61, the control device 3, and the communication line 60.
  • the management unit 21 stores the acquired slave device information IF, in the present embodiment, the first slave device information IFf in the storage unit 20M for each version of the slave device 5.
  • the storage unit 20M includes a plurality of device information storage units 20Mp1, 20Mp2, 20Mp3,... 20Mpn for each version of the slave device 5. n is an integer of 1 or more. The reason why the management unit 21 stores the slave device information in the separate device information storage units 20Mp1, 20Mp2, 20Mp3,...
  • 20Mn in units of versions is to manage the version of the slave device information acquired from each slave device 5. is there.
  • the device information storage units 20Mp1, 20Mp2, 20Mp3,... 20Mpn are not distinguished, they are referred to as device information storage units 20Mp.
  • the information request unit 22 transmits a request command for acquiring slave device information from the slave device 5 based on a command from the management unit 21.
  • the request command is transmitted to the slave device 5 via the communication unit 20T, the communication line 60, the control device 3, the first communication line 61, the first communication device 4F, and the second communication line 62.
  • the storage unit 20M stores a computer program for realizing the functions of the management unit 21 and the information request unit 22.
  • the processing unit 20C implements the functions of the management unit 21 and the information requesting unit 22 by reading the computer program from the storage unit 20M and executing it.
  • requirement part 22 may be implement
  • the management unit 21 and the information request unit 22 are implemented as software.
  • the functions of the management unit 21 and the information request unit 22 may be realized by cooperation of a plurality of processing circuits or a plurality of hardware.
  • the display device 2M displays the slave device information IF, in the present embodiment, the first slave device information IFf, displays information when managing the first slave device 51, and the control contents of the control device 3 Display information when changing or creating
  • the information displayed on the display device 2M is not limited to these.
  • the display device 2M is exemplified by a liquid crystal display panel.
  • the control device 3 is a device that controls a control target.
  • the control apparatus 3 is PLC, it is not limited to this.
  • the control device 3 may be a C language controller, a motion controller, or an inverter.
  • Control objects of the control device 3 are devices such as machine tools, robots, elevators, and boilers, and more specifically actuators provided in these devices.
  • the control device 3 controls the control object using information for controlling the control object.
  • information for controlling a control target is appropriately referred to as control information.
  • the control information is exemplified by a detection value detected by the sensor.
  • the first slave device 51 includes at least one of a device that gives control information to the control device 3 and a control target of the control device 3.
  • Examples of devices that provide control information to the control device 3 include various sensors such as an imaging device, a rotation angle detector, a speedometer, an accelerometer, a thermometer, a pressure gauge, and a photosensor.
  • the control target of the control device 3 is an electric motor, an air cylinder, a hydraulic cylinder, or a PLC different from the control device 3.
  • the first slave devices 51a, 51b, and 51c correspond to devices that give control information to the control device 3
  • the first slave devices 51d, 51e, and 51f correspond to control objects of the control device 3. .
  • the first communication device 4F is a device that relays communication between the control device 3 and the first slave device 51.
  • the first communication device 4F is a router, a layer 2 switch, or a bridge, and a bridge is used in the present embodiment.
  • the first communication device 4F is not limited to a bridge.
  • the relay of communication by the first communication device 4F is required because of the first communication method used for communication with the control device 3 and the second communication used for communication with the first slave device 51. This is because the method is different. That is, the first communication device 4F has two different communication methods existing between the control device 3 and the first slave device 51, that is, the mutual between the first communication method and the second communication method. Communication is relayed between the first communication line 61 and the second communication line 62 while guaranteeing the connection. Therefore, the control device 3 connected to the first communication line 61 and the first slave device 51 connected to the second communication line 62 can communicate with each other via the first communication device 4F. .
  • the first slave devices 51a, 51b, 51c shown in FIG. 4 are sensors.
  • the first slave devices 51a, 51b, 51c include a communication unit 501F that is a communication interface used for communication using the second communication method, a storage unit 502 that stores the first slave device information IFf, and a detection And a sensing unit 503 that outputs the result to the communication unit 501 and the storage unit 502.
  • the first slave devices 51d, 51e, and 51f include a communication unit 501S that is a communication interface used for communication using the second communication method, a storage unit 502 that stores the first slave device information IFf, and a target And an information collecting unit 504 that collects information about errors occurring in the devices and the state of the target device and stores the information in the storage unit 502.
  • the first slave device information IFf stored in the storage unit 502 is information set in the first slave device 51 in order to use the first slave device 51.
  • the first slave device information IFf represents a manufacturer information field 511 in which manufacturer information for identifying the manufacturer of the first slave device 51 is stored, and a device identification name of the first slave device 51.
  • a device name information field 512 including information on the type, model, function, and specification of the slave device 51, and an error information field 513 including a parameter describing the error type and error detected in the first slave device 51.
  • the manufacturer information field 511 includes a manufacturer code of the first slave device 51.
  • the device name information field 512 includes the ID of the first slave device 51.
  • the error information field 513 includes error information that is information related to the error of the first slave device 51.
  • the error information is an error code of the first slave device 51.
  • the error code indicates the type of abnormality that has occurred in the first slave device 51.
  • the device name information field 512 is provided with a version information subfield 512a in which the version of the first slave device 51 is described.
  • the first slave device 51 When the first slave device 51 detects an error that has occurred inside the first slave device 51, the first slave device 51 writes an error that has occurred in itself, that is, information relating to the error, in the error information field 513.
  • the first slave device 51 is a sensor, the first slave device 51 writes error information corresponding to the abnormal value, that is, an error code, in the error information field 513 when detecting the abnormal value.
  • FIG. 6 is a diagram showing an example of an error code table showing the correspondence between error codes and error contents.
  • FIG. 7 is a diagram illustrating a state in which the error code is displayed on the display device 2M.
  • the error code table describes combinations of error codes EC and error contents CT. There are as many combinations as the number of types of errors that occur in the first slave device 51.
  • the first slave device 51 outputs error information that can be read by the control device 3 and the management device 2, that is, an error code EC. That the control device 3 and the management device 2 can be decoded means that the error code EC is described in accordance with the protocol used by the control device 3 and the management device 2, and the control device 3 and the management device 2 mean the error code EC. Can be analyzed based on the device ID.
  • the processing unit 20C of the management device 2 acquires the error code EC
  • the error code EC is displayed on the display device 2M as shown in FIG.
  • the operator of the management system 1 is that the error that has occurred in the first slave device 51 is more than the transmission power supply drop.
  • the processing unit 20C may cause the display device 2M to display at least one of the error content, the manufacturer code of the first slave device 51, and the device ID in addition to the error code EC. That is, the processing unit 20C causes at least the error code EC in the first slave device information IFf to be displayed on the display device 2M.
  • the management system 1 stores the first slave device information IFf in the first slave device 51. Since the error code of the first slave device 51 is handled by the first slave device information IFf, that is, the data set of the manufacturer code, device ID, and error information of the first slave device 51, the error code EC is unique. Determined. For this reason, the management device 2 that is a higher-level device of the first slave device 51 acquires the first slave device information IFf together with the error code EC, so that it does not depend on the manufacturer type of the first slave device 51. , Error display can be made uniquely.
  • FIG. 8 is a flowchart showing an operation in which the management apparatus acquires slave device information in the management system according to the first embodiment.
  • the management unit 21 of the management device 2 illustrated in FIG. 2 starts from the first slave device 51 to the first slave.
  • a command for acquiring the device information IFf is given to the information request unit 22.
  • step S102 the information request unit 22 transmits a request command.
  • the request command is transmitted to the first slave device 51 via the communication line 60, the control device 3, the first communication line 61, the first communication device 4F, and the second communication line 62 shown in FIG.
  • the management apparatus 2 detects that a new first slave device 51 has been added to the management system 1 in the management system 1, the information request unit 22 sends a request command.
  • the first slave device 51 is upgraded, the corresponding first slave device 51 outputs that the version has been upgraded.
  • the management apparatus 2 acquires information on the version upgrade of the first slave device 51
  • the information request unit 22 transmits a request command.
  • the first slave device 51 in which the error has occurred outputs information for confirming the error.
  • the management apparatus 2 acquires information indicating that an error has been confirmed, the information request unit 22 transmits a request command.
  • the first slave device 51 that has received the request command outputs the first slave device information IFf and transmits it to the management device 2 via the first communication device 4F.
  • the first slave device 51 adds an error code EC corresponding to the generated error to the first slave device information IFf and outputs it.
  • the first slave device 51 includes a first slave device having an error information field 513 corresponding to the type of error that has occurred, from the first slave device information IFf stored in the storage unit 502. The device information IFf is selected and output.
  • the first slave device information IFf reaches the management device 2 via the second communication line 62, the first communication device 4F, the first communication line 61, the control device 3, and the communication line 60.
  • the first communication device 4F obtains the error information included in the first slave device information IFf, that is, the error code EC, from the first slave device 51
  • the content of the error code EC is not changed.
  • the contents are output to the management apparatus 2 while being held.
  • the management unit 21 of the management apparatus 2 acquires slave device information IFf.
  • step S105 when an error occurs in the first slave device 51, the management unit 21 displays the error code EC included in the first slave device information IFf on the display device 2M.
  • the management unit 21 stores the acquired slave device information IFf in the storage unit illustrated in FIG. It is stored in the 20M device information storage unit 20Mp.
  • step S106 when a new first slave device 51 is added to the management system 1 or when the first slave device 51 is upgraded, the management unit 21 stores the device information storage unit of the storage unit 20M.
  • the first slave device 51 used by the control device 3 is set using the first slave device information IFf stored in 20 Mp. That is, the management unit 21 sets the first slave devices 51 a, 51 b, 51 c that transmit control information and the first slave devices 51 d, 51 e, 51 f to be controlled by the control device 3 in the control device 3.
  • the control parameter of the first slave device 51 used by the control device 3 in the management system 1 is written to the storage unit of the control device 3, or the address or specification of the first slave device 51 is set to the control device 3.
  • the specification of the first slave device 51 includes the accuracy or performance limit value of the first slave 51.
  • step S101 if acquisition of the first slave device information IFf is not necessary (step S101, No), the acquisition processing of the first slave device information IFf according to the present embodiment ends.
  • the first slave device 51 is connected to the second communication line 62 of the management system 1 or the first slave device 51 is connected to the second communication line 62. This is a case where the slave device 51 is upgraded, the first slave device 51 detects an error, or an error occurs in the first slave device 51 itself.
  • the error code EC of the first slave device 51 is handled by a data set of the manufacturer code, device ID, and error information of the first slave device 51 included in the first slave device information IFf. Therefore, it is uniquely determined.
  • the first slave device 51 stores such first slave device information IFf.
  • the first slave device 51 outputs an error code EC corresponding to the error together with the first slave device information IFf.
  • the management device 2 that is a higher-level device of the first slave device 51 acquires and displays the error code EC corresponding to the error that has occurred in the first slave device 51 by acquiring the first slave device information IFf. Since the information is displayed on the device 2M, an error can be uniquely displayed without depending on the manufacturer type of the first slave device 51.
  • the management device 2 stores the first slave device information IFf corresponding to the version of the first slave device 51. Specifically, the management unit 21 of the management device 2 reads the version of the first slave device 51 described in the version information subfield 512a of the acquired first slave device information IFf. Then, the management unit 21 stores the acquired first slave device information IFf in the device information storage unit 20Mp of the storage unit 20M corresponding to the read version. In this way, the storage unit 20M of the management device 2 can store the first slave device information IFf corresponding to the version of the first slave device 51. As a result, even when a plurality of versions of the first slave devices 51 are mixed in the management system 1, the management device 2 can set the first slave devices 51.
  • the first slave device 51 stores the first slave device information IFf.
  • the first communication device 4F may store the first slave device information IFf.
  • the first slave device 51 that has received the request command transmitted from the information request unit 22 transmits the request command to the first communication device 4F.
  • the first communication device 4F transmits the first slave device information IFf to the management device 2 in step S103. Subsequent processing is as described above.
  • the management device 2 stores the first slave device information IFf of a version different from the stored first slave device information IFf. Specifically, the management unit 21 of the management device 2 reads the version of the first slave device 51 described in the version information subfield 512a of the acquired slave device information IFf. Then, the management unit 21 stores the acquired first slave device information IFf in the device information storage unit 20Mp of the storage unit 20M corresponding to the read version. In this way, the storage unit 20M of the management device 2 can store the first slave device information IFf corresponding to the version of the first slave device 51.
  • the management device 2 acquires a first slave device information IFf having a version different from the stored first slave device information IFf.
  • a first slave device information IFf having a version different from the first slave device information IFf stored in the storage unit 20M will be described.
  • the first slave device 51 that has received the request command receives the first slave device 51 from the version information subfield 512a in which the version of the first slave device 51 is described. The version is read and transmitted to the management apparatus 2.
  • step S104 the management unit 21 of the management device 2 acquires the version of the first slave device 51. Then, the device information storage unit 20Mp of the storage unit 20M is searched to confirm the existence of the first slave device information IFf whose version matches the acquired version of the first slave device 51. When there is a version of the first slave device information IFf that matches the version of the acquired first slave device 51, the acquired first slave device information IFf is stored in the storage unit 20M. The slave device information IFf is the same version. In this case, the management unit 21 does not acquire the first slave device information IFf from the first slave device 51.
  • the storage unit 20M stores the acquired first slave device information IFf.
  • the version is different from the stored first slave device information IFf.
  • the management unit 21 causes the information request unit 22 to issue a request command for requesting transmission of the first slave device information IFf.
  • the first slave device 51 that has received this request command receives the first slave device information IFf including all of the manufacturer information field 511, the device name information field 512, the version information subfield 512a, and the error information field 513. It transmits to the management apparatus 2.
  • step S105 the management unit 21 stores the acquired slave device information IFf in the device information storage unit 20Mp of the storage unit 20M illustrated in FIG. Since the device information storage unit 20Mp is provided for each version of the first slave device 51, the version of the acquired first slave device information IFf and the first slave device information IFf stored in the storage unit 20M. Are different, a device information storage unit 20Mp is newly created in the storage unit 20M. The acquired first slave device information IFf is stored in the newly created device information storage unit 20Mp.
  • the management system 1 can reduce the communication amount of the communication line 60, the first communication line 61, the first communication device 4F, and the second communication line 62.
  • FIG. 9 is a diagram illustrating a modification of the management system according to the first embodiment.
  • the management system 1 ′ according to the modified example includes first communication lines 61 and 61 ′ that form the network 11, and slave devices 53a and 53b are also connected to the first communication line 61 ′.
  • the slave devices 53a and 53b are referred to as first slave devices 53a and 53b, and when not distinguished from each other, they are appropriately referred to as the first slave device 53.
  • the first slave device 53 is not connected to the first communication device 4F.
  • the first slave device 53 is connected to the control device 3 and directly communicates with the control device 3.
  • the first slave devices 53a and 53b communicate with the control device 3 using the first communication method.
  • the first slave devices 53a, 53b have the same configuration as the first slave devices 51a, 51b, 51c or the first slave devices 51d, 51e, 51f shown in FIG. 4 or FIG. That is, each of the first slave devices 53a and 53b stores its own slave device information IF.
  • the management device 2 acquires slave device information via the communication line 60, the control device 3, and the first communication lines 61 and 61 '.
  • the management device 2 and the control device 3 exchange information with the first slave devices 53a and 53b without going through the first communication device 4F.
  • the management device 2 exchanges information with the first slave devices 53 a and 53 b via the control device 3. That is, the error code included in the first slave device information IFf output from the first slave devices 53 a and 53 b is acquired by the management device 2 via the control device 3.
  • the first communication device 4F may store the first slave device information IFf of the first slave device 53. In this way, by storing the first slave device information IFf in the first communication device 4F on the downstream side of the control device 3, it is not necessary to change the control device 3. As a result, the configuration of the management system 1 is simplified.
  • the first communication device 4F stores the first slave device information IFf of the first slave device 53
  • the first slave device that has received the request command transmitted from the information request unit 22 in step S102 described above. 53 transmits a request command to the control device 3.
  • the control device 3 transmits the received request command to the first communication device 4F.
  • the first communication device 4F transmits the first slave device information IFf of the first slave device 53 to the management device 2. Subsequent processing is as described above.
  • the management system 1, 1 ′ handles the data set of the manufacturer code, the device ID, and the error information, that is, the error code EC, of the first slave devices 51 and 53 as the first slave device information IFf.
  • the code EC is uniquely determined.
  • the management system 1, 1 ′ acquires such first slave device information IFf, acquires an error code EC corresponding to the error that has occurred in the first slave devices 51, 53, and displays it on the display device 2M. Therefore, an error can be uniquely displayed without depending on the manufacturer type of the first slave devices 51 and 53.
  • the management device 2 acquires the first slave device information IFf via the control device 3, and sets the first communication device 4 F between different communication methods existing in the network 11. Intervene. In this way, the management systems 1 and 1 ′ do not need to upgrade the engineering tool realized by the management apparatus 2 and import the first slave device information IFf into the engineering tool. It is possible to correctly recognize the first slave device 51 connected to, and to monitor and set the recognized first slave device 51.
  • the first communication method and the second communication method are different in the first embodiment, they may be the same. The configurations of the first embodiment and the modifications thereof can be applied or combined as appropriate in the following embodiments.
  • FIG. FIG. 10 is a diagram illustrating a management system according to the second embodiment.
  • the management system 1a according to the second embodiment is the same as the management system 1 according to the first embodiment, but is a slave device that communicates using a third communication method different from the second communication method.
  • the second slave device 52a, 52b, 52c communicates with the control device 3 using the first communication method, and communicates with the second slave device 52a, 52b, 52c using the third communication method. 3 and a second communication device 4S, which is a communication device that relays between the second slave devices 52a, 52b, and 52c.
  • the management device 2 includes the second communication device 4S via the control device 3 and the second communication device 4S.
  • the second slave device 52a, 52b, 52c acquires the information of the second slave device 52a, 52b, 52c, that is, the second slave device information IFs, which is slave device information, and stores it. Others are the same as those of the management system 1, and the management apparatus 2 is also the same as that of the first embodiment.
  • the acquisition processing of the first slave device information IFf according to the first embodiment is also performed for the processing in which the management device 2 of the management system 1a acquires and sets the second slave information IFs from the second slave device 52. This can be applied in the same manner as in the first embodiment.
  • slave devices 53a and 53b shown in FIG. 7 may be connected to the first communication line 61. In the following, differences from the first embodiment will be mainly described.
  • the second slave devices 52a, 52b, and 52c are not distinguished, they are referred to as second slave devices 52.
  • the second slave device 52 is the same as the first slave device 51 described in the first embodiment. That is, when the second slave device 52 is a sensor, the second slave device 52 has the same configuration as the first slave devices 51a, 51b, 51c shown in FIG.
  • the second slave device 52 is a control target of the control device 3
  • the second slave device 52 has the same configuration as the first slave devices 51d, 51e, and 51f shown in FIG.
  • the control device 3 and the second communication device 4S are connected by a first communication line 61.
  • the second communication device 4S and the second slave devices 52a, 52b, 52c are connected by a third communication line 63.
  • the management system 1a In addition to the first slave devices 51a, 51b, 51c, 51d, 51e, and 51f, the management system 1a also manages the second slave devices 52a, 52b, and 52c.
  • the third communication line 63 is a communication line used for communication using the third communication method.
  • the third communication method is different from the first communication method and the second communication method, but may be different from at least the second communication method. Further, the third communication method may be the same as the first communication method and the second communication method.
  • the management system 1 a manages the second slave device 52 in addition to the first slave device 51.
  • the management of the first slave device 51 is as described above.
  • Management of the second slave device 52 includes setting a control parameter or specification of the second slave device 52 in the control device 3.
  • the management of the second slave device 52 is performed when a new second slave device 52 is connected to the network 11 of the management system 1a or when the connected second slave device 52 is updated.
  • the setting of the state of the device configuration of the second slave device 52 in the control device 3 is also included.
  • the management device 2 sets the first slave device 51 and the second slave device 52 in the control device 3, the management device 2 passes the first communication device 4F and the second communication device 4S through the first communication device 4F.
  • the first slave device information IFf and the second slave device information IFs from the first slave device 51 and the second slave device 52 are acquired.
  • the management system 1a like the management system 1 according to the first embodiment, is based on the versions of the first slave device 51 and the second slave device 52, and the first slave device information IFf and the second slave device information IFf. Since the slave device information IFs is managed, the first slave device 51 and the second slave device 52 can be set according to the versions of the first slave device 51 and the second slave device 52. Therefore, the management system 1a does not need to include a plurality of engineering tools.
  • the first slave device information IFf or the second slave device information IFf2 exists in the engineering tool realized by the management device 2
  • the first slave device information IFf or the second slave device information IFf in the engineering tool of the management device 2 exists.
  • 2 slave device information IFs can be set.
  • the configuration described in the above embodiment shows an example of the contents of the present invention, and can be combined with another known technique, and can be combined with other configurations without departing from the gist of the present invention. It is also possible to omit or change the part.

Landscapes

  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Engineering & Computer Science (AREA)
  • Automation & Control Theory (AREA)
  • Small-Scale Networks (AREA)
  • Programmable Controllers (AREA)
  • Testing And Monitoring For Control Systems (AREA)

Abstract

L'invention concerne un système de gestion pourvu de : un appareil de commande ; un appareil esclave ; un appareil de communication, qui communique avec l'appareil de commande et l'appareil esclave, et qui effectue le relais entre l'appareil de commande et l'appareil esclave ; et un dispositif de gestion qui acquiert des informations relatives à l'appareil esclave, c'est-à-dire des informations de l'appareil esclave, par l'intermédiaire de l'appareil de commande. Les informations de l'appareil esclave sont mémorisées dans l'appareil esclave et/ou l'appareil de communication.
PCT/JP2015/060386 2015-04-01 2015-04-01 Système de gestion WO2016157477A1 (fr)

Priority Applications (4)

Application Number Priority Date Filing Date Title
KR1020177031475A KR101849512B1 (ko) 2015-04-01 2015-04-01 관리 시스템
JP2016559381A JP6177455B2 (ja) 2015-04-01 2015-04-01 管理システム
CN201580078436.5A CN107430391B (zh) 2015-04-01 2015-04-01 管理系统
PCT/JP2015/060386 WO2016157477A1 (fr) 2015-04-01 2015-04-01 Système de gestion

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2015/060386 WO2016157477A1 (fr) 2015-04-01 2015-04-01 Système de gestion

Publications (1)

Publication Number Publication Date
WO2016157477A1 true WO2016157477A1 (fr) 2016-10-06

Family

ID=57004119

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2015/060386 WO2016157477A1 (fr) 2015-04-01 2015-04-01 Système de gestion

Country Status (4)

Country Link
JP (1) JP6177455B2 (fr)
KR (1) KR101849512B1 (fr)
CN (1) CN107430391B (fr)
WO (1) WO2016157477A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018070190A1 (fr) * 2016-10-14 2018-04-19 オムロン株式会社 Dispositif informatique et système de commande
JP2020088690A (ja) * 2018-11-28 2020-06-04 オムロン株式会社 制御装置、サポート装置、および通信システム
WO2020137343A1 (fr) 2018-12-28 2020-07-02 オムロン株式会社 Dispositif de support, programme d'assistance et appareil de commande
WO2020137345A1 (fr) 2018-12-28 2020-07-02 オムロン株式会社 Système de commande, appareil de commande et procédé de commande

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH10214120A (ja) * 1997-01-29 1998-08-11 Murata Mfg Co Ltd 熱処理設備の制御システム
JP2001255911A (ja) * 2000-03-13 2001-09-21 Yaskawa Electric Corp プログラマブルコントローラのパラメータ設定方法
JP2002268730A (ja) * 2001-03-09 2002-09-20 Mitsubishi Electric Corp フィールドデバイスのメンテナンス装置
JP2005234926A (ja) * 2004-02-20 2005-09-02 Yokogawa Electric Corp メッセージサーバ
JP2006268476A (ja) * 2005-03-24 2006-10-05 Murata Mfg Co Ltd 熱処理設備システム
JP2009301469A (ja) * 2008-06-17 2009-12-24 Yokogawa Electric Corp 温調計システム

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2009301468A (ja) * 2008-06-17 2009-12-24 Yokogawa Electric Corp 温調計システム
JP6042243B2 (ja) * 2013-03-18 2016-12-14 株式会社日立ソリューションズ 監視システム、監視サーバ及び監視方法

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH10214120A (ja) * 1997-01-29 1998-08-11 Murata Mfg Co Ltd 熱処理設備の制御システム
JP2001255911A (ja) * 2000-03-13 2001-09-21 Yaskawa Electric Corp プログラマブルコントローラのパラメータ設定方法
JP2002268730A (ja) * 2001-03-09 2002-09-20 Mitsubishi Electric Corp フィールドデバイスのメンテナンス装置
JP2005234926A (ja) * 2004-02-20 2005-09-02 Yokogawa Electric Corp メッセージサーバ
JP2006268476A (ja) * 2005-03-24 2006-10-05 Murata Mfg Co Ltd 熱処理設備システム
JP2009301469A (ja) * 2008-06-17 2009-12-24 Yokogawa Electric Corp 温調計システム

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018070190A1 (fr) * 2016-10-14 2018-04-19 オムロン株式会社 Dispositif informatique et système de commande
JP2018063612A (ja) * 2016-10-14 2018-04-19 オムロン株式会社 演算装置および制御システム
CN109716247A (zh) * 2016-10-14 2019-05-03 欧姆龙株式会社 运算装置以及控制系统
CN109716247B (zh) * 2016-10-14 2021-09-17 欧姆龙株式会社 运算装置以及控制系统
JP2020088690A (ja) * 2018-11-28 2020-06-04 オムロン株式会社 制御装置、サポート装置、および通信システム
WO2020110668A1 (fr) 2018-11-28 2020-06-04 オムロン株式会社 Dispositif de commande, dispositif de support et système de communication
JP7159818B2 (ja) 2018-11-28 2022-10-25 オムロン株式会社 制御装置および通信システム
WO2020137343A1 (fr) 2018-12-28 2020-07-02 オムロン株式会社 Dispositif de support, programme d'assistance et appareil de commande
WO2020137345A1 (fr) 2018-12-28 2020-07-02 オムロン株式会社 Système de commande, appareil de commande et procédé de commande

Also Published As

Publication number Publication date
KR101849512B1 (ko) 2018-04-16
CN107430391B (zh) 2019-01-11
JPWO2016157477A1 (ja) 2017-04-27
KR20170129951A (ko) 2017-11-27
JP6177455B2 (ja) 2017-08-09
CN107430391A (zh) 2017-12-01

Similar Documents

Publication Publication Date Title
JP5927242B2 (ja) 画像データ作成装置および携帯端末装置
US9398097B2 (en) Method for servicing a field device
KR102042664B1 (ko) 데이터 수집 장치, 데이터 수집 방법 및 기록 매체
JP6177455B2 (ja) 管理システム
EP1351108A1 (fr) Procede et appareil de programmation
EP1705540B1 (fr) Méthode d'ouverture d'un réseau dans un système de production
JP6673050B2 (ja) 機器保全装置、機器保全システム、機器保全方法、機器保全プログラム及び記録媒体
WO2015121930A1 (fr) Dispositif de traçage et système de commande
JP5146656B2 (ja) Ｆａ機器並びにファイルアクセスシステム
JP5190796B2 (ja) フィールド機器およびこれを用いたフィールド機器ソフトウェア更新システム
JP2019074880A (ja) 設定システム、設定装置、設定方法、及び設定プログラム
US20180099413A1 (en) Robot system and maintenance method for tracking information of module
JP2009205243A (ja) フィールド機器管理装置、フィールド機器管理システム、フィールド機器管理方法、コンピュータプログラム、記録媒体
JP6408277B2 (ja) データ収集装置及び産業用ネットワークシステム
JP5792866B2 (ja) プロフィバスｄｐのマスタ装置
JP2010287034A (ja) 外部機器とＰＬＣとのＭｏｄｂｕｓプロトコル通信アドレス表示方式
JP6784271B2 (ja) 変更検出装置、保全管理システム、変更検出方法、プログラムおよび記録媒体
JP2014142823A (ja) データ作成装置および方法
KR101655727B1 (ko) 프로그래머블 컨트롤러 및 프로그래머블 컨트롤러의 제어 방법
JP2006318102A (ja) フィールド機器管理装置およびフィールド機器管理方法
US20190303319A1 (en) Support apparatus, non-transitory computer-readable recording medium and setting method
JP7379948B2 (ja) サポート装置、サポートプログラムおよび設定方法
JP6833109B1 (ja) データ収集装置、データ収集方法及びプログラム
US11580473B2 (en) Engineering support system, engineering support method, client device, and storage medium
JP6051545B2 (ja) Ｐｌｃシステム、状態表示方法、ｐｌｃ、およびプログラマブル表示器

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 2016559381

Country of ref document: JP

Kind code of ref document: A

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15887624

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20177031475

Country of ref document: KR

Kind code of ref document: A

122 Ep: pct application non-entry in european phase

Ref document number: 15887624

Country of ref document: EP

Kind code of ref document: A1