JP5030852B2 - Device management apparatus, device management method, and program - Google Patents

Device management apparatus, device management method, and program Download PDF

Info

Publication number
JP5030852B2
JP5030852B2 JP2008116500A JP2008116500A JP5030852B2 JP 5030852 B2 JP5030852 B2 JP 5030852B2 JP 2008116500 A JP2008116500 A JP 2008116500A JP 2008116500 A JP2008116500 A JP 2008116500A JP 5030852 B2 JP5030852 B2 JP 5030852B2
Authority
JP
Japan
Prior art keywords
device
information
connected
network
profile
Prior art date
Legal status (The legal status 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 status listed.)
Active
Application number
JP2008116500A
Other languages
Japanese (ja)
Other versions
JP2009266047A (en
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 JP2008116500A priority Critical patent/JP5030852B2/en
Publication of JP2009266047A publication Critical patent/JP2009266047A/en
Application granted granted Critical
Publication of JP5030852B2 publication Critical patent/JP5030852B2/en
Application status is Active legal-status Critical
Anticipated expiration legal-status Critical

Links

Images

Description

  The present invention relates to a technology for diagnosing the health of transmission lines and devices included in a communication system, and more particularly to a technology for diagnosing the health of transmission lines and devices in a control system.

  In the conventional control system, each device included in the control system has a dedicated tool, and diagnosis is performed by connecting a separate dedicated tool to the device. However, in recent years, control systems have become large-scale, and the network configuration has become complicated accordingly.

A network that can be connected to a control device such as a programmable logic controller (PLC) or a display device includes an information network that connects to a higher-level information system such as a plan server and a management server, a controller network that connects PLCs, and between PLCs and field devices. It is classified into three types of field network connection.
Further, each network has a different one for each vendor or organization.
For example, in the case of a field network, there are CC-Link, PROFIBUS mainly used in Europe, and DeviceNet mainly used in the United States.
These networks do not operate normally unless various parameters depending on the communication form are set for appropriate devices.
However, as the system configuration becomes complicated, the occurrence rate of setting errors increases.

At present, when an abnormality occurs in a network or device, the location and cause of the abnormality must be identified individually using a dedicated tool.
However, in general, users using FA devices are often specialists in control systems, but they are not necessarily network specialists, so it takes time to identify abnormalities and causes. Extra costs are incurred in building production lines, such as increased turnaround time.

In a conventional supervisory control system, an operation simulation data program for each device category is described in the profile, and if there is an important signal directly related to the control of the external drive device for the detected connected device, System safety is provided by extracting simulation data from a profile and performing an operation simulation in which the output is masked before executing direct output processing using the extracted simulation data (see, for example, Patent Document 1).
Japanese Patent Laid-Open No. 11-231927 (page 9, paragraphs 71-74, FIG. 12)

In a system connected by a network, in order to diagnose each device from a single location via the network, the environment must be able to communicate normally.
However, the monitoring and control system described in Patent Document 1 is premised on an environment in which correct network settings are performed and communication can be performed normally, and after all troublesome work such as checking the health of the transmission path is manually performed. There is a problem that must be done.
In addition, when the network configuration becomes complicated, there is a problem that work must be performed while considering the order in which diagnosis should be performed.

  The main object of the present invention is to solve the above-mentioned problems, and in a communication system including a control system, the main object is to efficiently and accurately diagnose the health of devices and transmission paths. And

The device management apparatus according to the present invention
A device management device that manages multiple types of devices connected to a managed network,
For each device type, a profile information storage unit that stores profile information in which a diagnosis procedure for diagnosing the state of the device is described;
An information collection unit for receiving notification information for notifying the device type of each device connected to the managed network;
A diagnostic processing unit for acquiring corresponding profile information based on the device type notified in the notification information received by the information collecting unit, and diagnosing the status of each device according to a diagnostic procedure using the acquired profile information; It is characterized by having.

  According to the present invention, by preparing profile information describing a diagnostic procedure for each device type and collecting notification information for notifying the device type from each device connected to the management target network, the device management apparatus The status of each device can be diagnosed according to an appropriate diagnostic procedure using profile information corresponding to the device type, reducing the complicated work of the user judging and diagnosing individual dedicated tools and diagnostic procedures for each device Therefore, setting mistakes can be avoided, and an abnormal location and cause can be identified early.

Embodiment 1 FIG.
Hereinafter, a control system design support apparatus (equipment management apparatus) according to the present embodiment will be described with reference to the drawings.
The control system design support apparatus according to the present embodiment manages a device connected to the management target network using a network of a control system such as a FA (Factory Automation) system as the management target network.
For example, the control system design support apparatus according to the present embodiment determines the order in which the transmission path and the device are diagnosed from the connection relationship grasped from the detected contents in the control system, and describes the diagnosis procedure for each device. Using the profile, the health of the device and the transmission path is confirmed in the order of diagnosis determined from the connection relationship. And it detects the abnormality of equipment and transmission lines, simple connection errors, etc., and realizes system startup and ease of maintenance.

(Description of control system design support device)
A configuration example of the control system design support apparatus 1 according to the present embodiment is shown in FIG.
Here, before describing details of each component of the control system design support apparatus 1, an outline of the operation of the control system design support apparatus 1 will be described.
The profile database 3 stores a profile 20 in which a diagnostic procedure is described for each device type included in the control system.
And ID information collection part 6 collects ID information and user designation information from each apparatus which constitutes a control system.
Although details of the ID information and user designation information will be described later, the device type can be extracted from the description of the ID information and user designation information.
In addition, the diagnosis processing unit 8 acquires a profile 20 corresponding to the device type extracted from the ID information and the user-specified information, and the diagnosis processing unit 8 performs normality for each transmission path for each device according to the diagnosis procedure indicated in the profile 20. Diagnose.
Further, the configuration management information management unit 5 generates network configuration information 10 indicating the network configuration from the ID information collected by the ID information collection unit 6.
Further, the system configuration information management unit 4 generates network state information in which the diagnosis result from the diagnosis processing unit 8 is reflected in the network configuration information 10 and displays the network state information on the information display unit 13.
The above is the outline of the operation of the control system design support apparatus according to the present embodiment.
Below, each component of the control system design support apparatus 1 is demonstrated in detail.

  In FIG. 1, a control system design support apparatus 1 includes a configuration management database 2 that stores information related to the system configuration of a control system such as an FA system, and a profile database 3 that stores a profile 20 that describes attributes of devices and units. Have.

The configuration management database 2 manages the connection relationship between devices and units included in the control system as network configuration information 10.
The network configuration information 10 is classified into two system configuration elements 11 of Device (device) and Media (network) to express a connection relationship.
In the network configuration information 10 in FIG. 1, D represents Device and M represents Media.
A device, such as a device or unit, is to be recognized as one object by the system configuration information management unit 4 and refers to hardware having an individual identifier (information such as a serial number that can be uniquely identified by the system).
Media refers to a general transmission line that connects a plurality of devices such as a network such as Ethernet (registered trademark) and a bus for communicating between PLC units.

The profile database 3 manages device and unit profile information 20 (hereinafter referred to as profiles).
The profile 20 describes the diagnosis procedure for diagnosing the attributes of devices and units, and the health of the devices and transmission paths. Details of the profile 20 will be described later.
The profile database 3 must maintain a state of having a profile 20 for a device or unit that can be connected.
Therefore, when a new type of device or unit is manufactured, or when the F / W (Firmware) version of the device or unit is changed, the profile database 3 is updated by adding or changing the profile 20. .
For example, the new profile 20 may be taken into the profile database 3 via a storage medium such as a CD (Compact Disc) -ROM (Read Only Memory) or a USB (Universal Serial Bus) memory.
Alternatively, a profile server that always manages the latest profile 20 may be installed, and a new profile 20 or a modified profile 20 may be downloaded from the profile server via a network.
The profile database 3 is an example of a profile information storage unit or a profile information storage area.

In the present embodiment, among the elements managed in the configuration management database 2, a profile 20 is prepared for each device.
Each device managed as the network configuration information 10 in the configuration management database 2 is associated with a profile 20 dedicated to the device among the profiles 20 stored in the profile database 3.
Since the profile 20 is prepared in units of type 65, if there are a plurality of devices of the same type 65 in the network configuration information 10, each is associated with the same profile 20. That is, the device and the profile 20 have an N: 1 relationship.

  The control system design support apparatus 1 includes a system configuration information management unit 4, a configuration management information management unit 5, an ID information collection unit 6, a profile inquiry unit 7, a diagnosis processing unit 8, a user instruction input unit 12, and an information display unit 13. Consists of

The system configuration information management unit 4 generates network status information indicating the layout of the control system and the status of devices and transmission paths included in the control system in accordance with the connection relationship of the actual devices.
The system configuration information management unit 4 is an example of a state information generation unit.
The system configuration information management unit 4 generates network state information in which the diagnosis result of each device and transmission path by the diagnosis processing unit 8 is reflected on the network configuration information generated by the configuration management information management unit 5 described later.
That is, the system configuration information management unit 4 associates the diagnosis results from the diagnosis processing unit 8 with each device indicated in the network configuration information generated by the configuration management information management unit 5 and connects to the control system. Network state information indicating the connection relationship between the devices and the diagnosis result for each device is generated.
For example, when an abnormality occurs in the control system, it is possible to visually notify the user by highlighting the location that caused the factor. Note that devices, units, and networks displayed in the system configuration information management unit 4 are collectively referred to as objects.
The devices described above include a programmable controller (PLC: Programmable Logic Controller, hereinafter abbreviated as PLC), a programmable display (HMI: Human Machine Interface), a numerical operation device (NC: Numerical Control), and a field device. (Sensors, valves, motors, servo amplifiers, inverters, robots, etc.)
The above-described unit refers to a component of the device. For example, the PLC becomes a single device by combining various types of units such as a base unit, a power supply unit, a CPU unit, an input / output unit, and a communication unit.
Also, in the programmable display, a communication unit or the like can be attached as an option separately from the device main body.
The network state information generated by the system configuration information management unit 4 is displayed by the information display unit 13.
The information display unit 13 provides a graphical interface to the user of the control system design support apparatus 1.

When the ID information collection unit 6 inputs an instruction from the user of the control system design support apparatus 1 via the user instruction input unit 12, the number of devices or units connected to the network, their models, Individual information 62 is collected.
As will be described later, the ID information of each device is an example of notification information for notifying the device type of each device, and the ID information collection unit 6 that collects ID information is an example of an information collection unit.

  The profile inquiry unit 7 specifies the profile 20 corresponding to the device and unit managed by the network configuration information 10 from the profile database 3.

The configuration management information management unit 5 analyzes the connection relationship of the actual devices (hereinafter referred to as network analysis), and generates network configuration information 10 indicating the connection relationship of each device from the analysis result.
The generated network configuration information 10 is stored in the configuration management database 2 and updated every time network analysis is performed.
Further, the configuration management information management unit 5 requests the system configuration information management unit 4 to generate network state information of the control system based on the network configuration information 10.
The configuration management information management unit 5 requests the ID information collection unit 6 to perform network analysis when the network configuration information 10 is newly generated or updated.
The configuration management information management unit 5 requests the profile inquiry unit 7 to search for the corresponding profile 20 using the ID information collected by the ID information collection unit 6 as a key.
Further, the configuration management information management unit 5 requests the diagnosis processing unit 8 to check the health of each device and network based on the network configuration information 10.
The configuration management information management unit 5 is an example of a configuration information generation unit.

Based on the device type extracted from the ID information received by the ID information collection unit 6, the diagnosis processing unit 8 acquires the corresponding profile 20 from the profile database 3 via the profile inquiry unit 7, and acquires the acquired profile 20 Use to diagnose the status of each device according to the diagnostic procedure.
The diagnosis processing unit 8 also diagnoses the state of the transmission path included in the control system.
As will be described later, the profile database 3 stores a profile 20 for each device type and for each user-defined attribute defined for each device by the user, and the ID information collection unit 6 includes a control system. ID information for notifying the device type of each device included in the user information and user-specified information for notifying user-defined attributes.
Then, the diagnosis processing unit 8 extracts the corresponding profile 20 from the profile database 3 based on the device type notified in the ID information received by the ID information collecting unit 6 and the user-defined attribute notified in the user designation information. Using the acquired profile 20, the state of each device is diagnosed according to a diagnostic procedure.

(Description of control system example)
FIG. 2 shows a configuration example of the control system.
In the example of FIG. 2, the control system includes one control system design support device 1, two PLCs 31 to 32, one servo amplifier 36, one inverter 38, one programmable display 40, and one unit. I / O39, and two temperature controllers (temperature controllers) 41 to 42 connected to the lower part of I / O39.
Each device is connected by a field network 30.

The PLCs 31 to 32 are configured by attaching various units to the base unit.
Specifically, the PLC 31 mounts the power supply unit 33, the CPU unit 34, and the field network communication unit 35 on the base unit.
The power supply unit 33 supplies power to the units attached to the base unit to which the respective power supply units 33 are attached.
The CPU unit 34 stores programs for controlling various units and parameter information of the various units on the same PLC 31, and determines the conditions of the various units on the same PLC 31 according to the stored parameter information and operates the stored programs. To control various units.
The communication unit 35 exists for each type of network and is a unit for communicating with other devices.
The field network communication unit 35 is connected to the controlled device by the field network 30 and is used by the PLC 31 to control the controlled device.

The servo amplifier 36 is a device that operates the servo motor 37 according to an operation command from the PLCs 31 and 32 with the servo motor 37 as a target. The servo motor 37 is provided with an encoder that detects information such as a rotation angle, a speed, and a direction. By feeding back the detected information to the servo amplifier 36, a deviation from the operation command from the PLCs 31 and 32 can be obtained. I try not to go out.
The inverter 38 is a device that can change the rotational speed of the motor freely or continuously for a three-phase squirrel-cage motor.
The programmable display 40 is a device having three types of roles: an operation display panel, a POP terminal, and an information data terminal. As an operation display board, it replaces push button switches and lamps, and provides character information and graphic information display and input functions using touch keys.
The information data terminal is used to display the current system configuration on the screen and to exchange information with the PLCs 31 to 32 and the personal computer via a memory card or a network.
The temperature controllers 41 to 42 are devices for controlling the temperature to be controlled to a constant value by ON / OFF control, PID control, or the like based on information acquired by the temperature sensors 43 to 44.
The temperature controllers 41 and 42 are connected to the I / O 39 by serial cables (RS232, RS485, etc.), respectively.
Further, the control system design support device 1 can be connected to an arbitrary device on the field network 30 by a USB cable or a serial cable.

In the present embodiment, the field network 30 will be described with CC-Link as an object.
In CC-Link, connected devices and units are called stations.
One master station device 32 (hereinafter referred to as a master station) exists in the CC-Link, and manages the other stations 31, 36, 39, 38, and 40.
In CC-Link, only the PLC can be the master station.
Stations 31, 36, 39, 38, and 40 other than the master station 32 are slave station devices (hereinafter referred to as slave stations).
In CC-Link, a number called a station number is assigned to identify devices on the same field network 30. It is specified that the station number of the master station 32 is fixed to 0. Also, slave stations are assigned in ascending order from 1.
In the example of FIG. 2, the station number of the servo amplifier 36 is 1, the station number of the I / O 39 is 2, the station number of the inverter 38 is 3, the station number of the programmable display 40 is 4, and the station number of the PLC 31 is 5.
Note that the station numbers are only for devices directly connected to the field network 30, and are devices connected to other transmission paths via the field network 30, such as temperature controllers 41 to 42 and temperature sensors 43 to 44. The control system design support device 1 is not assigned a station number.

(Description of ID information)
Each device and each unit has device identification information 60 (hereinafter referred to as ID information) inside.
In the system configuration example of FIG. 2, the two PLCs 31 to 32, the servo amplifier 36, the inverter 38, the programmable display 40, the I / O 39, and the two temperature controllers 41 to 42 each have ID information 60.
The data structure of the ID information 60 is shown in FIG.
The ID information 60 is information for uniquely identifying a device in the product system, and includes model information 61 indicating model-specific information and individual information 62 indicating device-specific information.
The ID information 60 is a fixed value and is information assigned by the manufacturer at the time of factory shipment.
The model information 61 is information for specifying the type of device or unit, and includes a model code 63, a manufacturer code 64, and a model code 65. This model information 61 is one of the keys for searching the profile 20.
The individual information 62 is information assigned to each device and unit in order to uniquely identify them, and corresponds to a manufacturing number 66 and a MAC address 67. Even when there are a plurality of devices of the same model, the individual information 62 can identify the device.

(Description of network configuration information 10)
FIG. 4 shows an example of the network configuration information 10. In this example, the control system of FIG. 2 is expressed by being decomposed into two types of system components 11 of Device and Media.
The Device manages information about itself and information indicating a relationship with other objects. The former is an item indicating the attribute of the device or unit, and includes, for example, ID information 60. The latter includes association information to Media.
Media manages information related to other devices in the network. For example, there are network number, PLC base unit to which each unit is attached, and association information to Device.
The connection to the field network 30 can be made by using an interface built in the device body or using a field network communication unit 35 prepared as an option separately from the device body. In the example, the servo amplifier 36, the inverter 38, and the programmable display 40 are described as the former devices.

In the example of FIG. 4, each device and each unit represents a main body portion as Device. Specifically, PLC # A31 is expressed as Device131. Other devices are similarly expressed, and a value obtained by adding 100 to a device number indicates a device number of the device.
The transmission path is expressed as Media. Specifically, the field network 30 is expressed as Media. Other transmission paths are similarly expressed, and a value obtained by adding 200 to the transmission path number indicates the media number of the transmission path.

(General description of the profile)
The profile 20 is used for the purpose of reducing the development amount of software such as an engineering environment, a setting tool, and a screen of the programmable display 40.
For example, parameters such as parameter settings and monitors differ only in the type of data handled depending on the model. Functions such as displaying a parameter list, displaying the current value of each parameter, and changing the set value of a specified parameter are software processes. Are the same.
Therefore, by sharing such processing with software, it is possible to obtain various models by simply acquiring data from the profile 20 corresponding to the device or unit to be operated without creating a dedicated module different for each model. There is merit to be able to cope.
The profile 20 for the field network 30 includes a GSD (Generic Station Description) file and an EDD (Electronic Device Description) file for PROFIBUS, an EDS (Electronic Data Sheet) file for DeviceNet, and the like. There is also a CSP (CC-Link System Profile) file for CC-Link.

(General profile contents)
The description contents of these profiles are specified by type. For example, the description items include file information, device information, parameter information, user interface information, processing procedure information, error information, and the like.
The file information describes the file name, generation date / time, last update date / time, and version.
In the device information, a manufacturer code 64, a device type, and a model 65 are described as device attributes. The device attributes are collected from the profile 20 stored in the profile database 3 and used to display a device list.
In the device information, a bitmap file indicating icons of devices and units to be displayed on the screen of the engineering environment and the programmable display 40 is described. When the layout diagram of the system configuration is displayed on the engineering environment or the display device, it is displayed using icons defined in this bitmap file.
The parameter information describes parameters that can be set or displayed. In the parameter setting screen, parameter information is acquired from the profile 20 and a parameter list is displayed according to the content.
In the user interface information, screen layout information is described. User interface information is used to determine the display format such as charts, images, and graphs, and the arrangement of menus and buttons.
In the processing procedure information, a real-time data acquisition procedure and a file operation procedure are described.
In the error information, a register indicating an error state and the content of an error message meaning in the register are described.

(Profile description)
In the present embodiment, in addition to the above information, a diagnostic procedure for confirming the health of the device and the transmission path is described as diagnostic information.
FIG. 5 shows an example of the profile 20 for the CC-Link communication unit 35 attached to the PLC. 5 is not described based on the format of the CSP file, but described based on the format according to the present embodiment.
A profile 20 is prepared for each type of device and each user-specified attribute to be described later.
The profile 20 includes device information, parameter information, diagnostic information, and error information.
The profile 20 only describes information necessary for explaining the processing according to the present embodiment, and even if there is other information (file information, user interface information, processing procedure information, etc.). good.
In the diagnosis information, diagnosis procedures are described in the order executed by the control system design support apparatus 1.
In the diagnosis method, (A) a specific area (parameter information or the like) indicating the state of the device is monitored and determined from the value of the area, and (B) the diagnosis function provided by the device is used to determine from the diagnosis result. There is a method of judging.

In the example of FIG. 5, TestSequenceN (N is a number) is the minimum unit of processing, and shows what processing is performed depending on the test type. In FIG. 5, four types of status check, command execution, diagnosis result determination, and parameter setting are given as examples. However, other types may be defined. Also, the description content of TestSequence may be different for each test type, and each defines necessary information.
In this unit, four pieces of parameter information are defined. RX0 is a parameter indicating a unit error, RX1 is a parameter indicating a data link error of its own station, RX3 is a parameter indicating a data link error of a station other than itself, and RXF is a parameter indicating that the unit is ready for operation is doing.
Further, the error information defines a state in which these parameters indicate an abnormality and an error message at that time. In ErrEntry1, when RX0 is 1, it indicates that “unit is abnormal”. In addition, ErrEntry5 is not limited to a specific parameter, and indicates that “the response is not returned from the request destination” when the error code is 0xB778.

(1) The state check corresponds to the above-described diagnosis method (A), and designates parameters used for diagnosis and a check range.
Hereinafter, a specific description will be given using Test Sequence 1 to Test Sequence 4.
First, check the health of the unit itself.
TestSequence1 is a confirmation of the health of the unit itself and indicates that RX0 is not in an error state defined by ErrEntry1. RX0 is a register of a device to be diagnosed. In TestSequence1, the value of the register RX0 is received from the diagnosis target device, and it is checked whether or not the received value is 1. That is, if the value of RX0 is not 1, it is determined as normal, and if the value of RX0 is 1, an error message (or error code) defined by ErrEntry1 is displayed. In the case of ErrEntry1, the message “Unit is abnormal” is displayed.
TestSequence2 is confirmation of whether the unit itself is in an operating state, and indicates that the value of the register RXF of the diagnosis target device is not an error state defined by ErrEntry4 (the value of RXF is not 0).
Next, the health of the transmission path is confirmed.
TestSequence3 is a determination as to whether or not communication is possible from the data link state of the unit itself, and confirms that the value of the register RX1 of the diagnosis target device is not an error state defined by ErrEntry2 (the value of RX1 is not 0) Indicates to do.
Test Sequence 4 indicates that each station on the network confirms the data link state, and confirms that the value of the register RX 3 of the diagnosis target device is not in the error state defined by ErrEntry 3 (the value of RX 3 is not 0).

(2) Command execution, (3) Diagnosis execution, and (4) Parameter setting correspond to the above-described diagnosis method (B).
In order to execute the diagnosis function of the device, there is a series of flows in which a command is executed and finally a determination is made from the diagnosis result. Some commands require parameter settings as preparations for executing the command, such as designation of target devices and switching of parameter groups.
Hereinafter, a specific description will be given using Test Sequence 5 to Test Sequence 7. This is a series of operations for performing the line test diagnosis provided by this unit.
Test Sequence 5 is a process of designating a test target as preparation for command execution, and sets a station number for SW0008. * Means to execute each of the stations that have collected ID information.
Test Sequence 6 indicates that a command code for line test diagnosis is set in SW0005 as a command execution method. In addition, the command completion determination method indicates that the SW004D is set to 1. Test Sequence 6 means that a command handshake (request / response) is performed by a register. In the field network (CC-Link) used in the FA system, some devices cannot perform message communication. In Test Sequence 6, a command handshake is performed using a register. That is, the control system design support device 1 sets a line test diagnosis command in the device register SW0005, and recognizes that the execution of the command is completed when the device register SW004D becomes 1.
Test Sequence 7 is a process for determining the health from the result of the command (diagnosis), and specifies the parameters used for the determination and the check range. Specifically, using the value of SW004D, it is determined to be normal if any of ErrEntry5 to ErrEntry7 (0xB778, 0xBA19, 0xBA1B) is satisfied, and if any of them corresponds, the corresponding error message (or error code) ) Is displayed. SW004D is a register that stores a result (diagnosis result) of a command executed by the diagnosis function of the device. The control system design support apparatus 1 receives the value of the register SW004D and determines the diagnosis result.

(Profile identification method)
The description content of the profile 20 may be changed by the setting by the physical switch provided by the device or unit, the communication protocol, or the upgrade of S / W (Software).
For example, in CC-Link, among items that can be selected from several options, communication protocol version 72 and the number of occupied stations 71 (indicating the number of stations occupied by the device) are included as items that affect the description content of profile 20. The size of the device memory space of the device changes depending on the number of occupied stations 71).
Therefore, the profile 20 is not prepared for each type 65, but is prepared for a combination of the type 65 and a value that can be set for the communication protocol version 72 / the number of occupied stations 71.
Since the profile 20 is prepared in such a unit, the profile 20 cannot be uniquely specified only by the model information 61 of FIG. Therefore, as shown in FIG. 6, user designation information 70 that can be changed by the user is provided, and the corresponding profile 20 is specified using information obtained by combining the device ID information 60 and the user designation information 70 as a key. Features. The user designation information 70 includes the number of occupied stations 71, a communication protocol version 72, and an S / W version 73.

(Operation procedure of the entire system)
Next, the operation procedure of the automatic diagnosis method using the profile 20 will be described by taking as an example the case where the control system design support apparatus 1 is directly connected to the PLC # A31.

(Operation procedure of ID information collection unit)
FIG. 7 shows a procedure of a collection protocol of ID information 60 and user designation information 70 from each device via the transmission path. 8 and 9 show the operation procedure of the ID information collection unit 6.
First, the ID information collection unit 6 receives the request from the configuration management information management unit 5 and collects the ID information 60 and the user designation information 70 from each device on the transmission path, thereby connecting / connected. Detect equipment.
Specifically, the ID information collection unit 6 receives the ID information 60 and the user designation information 70, and is attached to a connected station (hereinafter referred to as a connected station), that is, PLC # A31. A communication unit is detected (S201) (information collecting step).
In the example of FIG. 2, since only one communication unit 35 is attached to the PLC #A 31, only one field network 30 is automatically diagnosed. If a plurality of communication units are attached to the PLC, automatic diagnosis is performed for each network.
The ID information collection unit 6 requests the diagnosis processing unit 8 to diagnose the health of the device directly connected to the control system design support apparatus 1 (S202).
The diagnosis processing unit 8 acquires the corresponding profile 20 via the profile inquiry unit 7 based on the ID information 60 and the user designation information 70 collected by the ID information collection unit 6 (profile information acquisition step), and acquires the acquired profile The target device is diagnosed in accordance with the diagnostic procedure 20 (diagnosis processing step).
If a device error is detected, the process ends in error.
The ID information collection unit 6 requests the diagnosis processing unit 8 to diagnose the health of the transmission path (S203).
In the diagnosis processing unit 8, the transmission path is diagnosed according to the diagnosis procedure shown in the profile 20 acquired in the instruction of S202.
If a transmission line error is detected, the process ends in error.
Next, if the transmission path is normal, the ID information collection unit 6 finds the master station 32 in the field network 30 to which the communication unit 35 detected in S201 is connected (S204) (information collection step). Specifically, CC-Link stipulates that the master station is set to station number 0. Therefore, the station with station number 0 may be searched. In the example of FIG. 2, PLC # B32 is the master station.
Next, the ID information collection unit 6 requests the master station 32 for ID information 60 and user designation information 70 of all devices directly connected to the field network 30 (S205).

When there is a request from the control system design support device 1, the master station 32 first detects the number of connected devices directly connected to the transmission path by polling and the directly connected devices, and detects each detected device. ID information 60 / user designation information 70 is obtained from the information.
The master station 32 receives the request from the control system design support apparatus 1 (S101), and requests the ID information 60 and the user designation information 70 from the slave station one by one from the station number 1 (S102). This request is made station by station in ascending order of station numbers from the station with station number 1 to the station with the largest station number that can be taken by the field network 30.
When receiving the request from the master station 32, the slave station responds with its own ID information 60 and user designation information 70 to the master station 32 (S103). When there is no response to the request, the master station 32 determines that there is no slave station with the station number on the transmission path.
The master station 32 responds to the control system design support apparatus 1 when the collection of the ID information 60 and the user designation information 70 for the number of slave stations is completed (S104).

When the control system design support device 1 completes the detection of the directly connected devices by polling of the master station 32 (S206), the control system design support device 1 transmits a lower transmission path (hereinafter referred to as a channel) to each device. The presence / absence, the number of devices connected by the channel, and the connected devices are detected, and ID information 60 / user designation information 70 is acquired from each detected device (information collecting step).
The ID information collection unit 6 requests the profile inquiry unit 7 to search the corresponding profile 20 from the profile database 3 using the ID information 60 and user designation information 70 of the slave station directly connected to the field network 30 as keys. (S207) (profile information acquisition step).
Next, the ID information collection unit 6 requests the diagnosis processing unit 8 to diagnose the health of each slave station directly connected to the master station 32 (S213).
The diagnosis processing unit 8 acquires the corresponding profile 20 from the ID information collection unit 6 and diagnoses the target device according to the diagnosis procedure indicated in the acquired profile 20 (diagnosis processing step).
When a device abnormality is detected (when the diagnosis result is abnormal in S214), if there is another device that has not been diagnosed, the processing from S207 onward is repeated to diagnose all the devices. If so, the process proceeds to S211.

When the device is normal (when the diagnosis result is normal in S214), the ID information collection unit 6 determines whether the device has a channel from the contents described in the profile 20 of each device. Determination is made (S208). No further processing is performed for devices that do not have a channel (in the case of no S209).
For a device with a channel (when S209 is present), the ID information collection unit 6 determines the number of channels, the presence / absence of devices connected to each channel, the number of devices, and the type of device for that device. The connected device on the channel is detected by making an inquiry (S210). In the example of FIG. 2, since only the I / O 39 has a channel, the ID information collection unit 6 makes an inquiry only to the I / O 39 (S105). The I / O 39 returns its own information to the ID information collection unit 6 (S106).
That is, the profile 20 indicates whether or not there is a possibility that a channel exists in each device (possibility that a lower device is connected). If there is no possibility that a channel exists with reference to the profile 20 If it is determined in S209 that there is no channel and there is a possibility that a channel exists, in S210, the number of channels, the presence / absence of devices connected to each channel, and the like are investigated.
If there is a device on the channel, the processing of S207 to S210 is performed on each device on the channel.
If there is no device on the channel (when there is no device at S209), the processing at S207 to S210 is performed on the next slave station.
When the processing from S207 onward is completed for all slave stations and devices on all channels, the ID information collection unit 6 sends the collected ID information 60 and user designation information 70 to the configuration management information management unit 5. At the same time (S211), it notifies that the ID information collection has been completed (S212).

Upon receiving the ID information collection completion notification from the ID information collection unit 6, the configuration management information management unit 5 recognizes the device connection based on the ID information 60 collected from each device on the transmission path and the user designation information 70. The relationship is generated as network configuration information 10.
FIG. 10 shows a procedure for generating the network configuration information 10 by the configuration management information management unit 5.

First, the configuration management information management unit 5 generates a device for each device connected to the field network 30 and the channel (S301).
The configuration management information management unit 5 searches the profile database 3 for the profile 20 corresponding to each device using the ID information 60 and the user designation information 70 received from the ID information collection unit 6 as keys (S302).
Next, the configuration management information management unit 5 extracts and sets items (manufacturer code 64, model code 63, model 65, etc.) indicating the attributes of the device or unit from the profile 20 corresponding to each station in each device. (S303).
Next, the configuration management information management unit 5 generates Media for the transmission path (S304). In Media, a network type, a network number, and the number of connected nodes are set (S305). In the example of FIG. 2, a value indicating CC-Link is set as the network type. Since CC-Link does not have a network number, the network number is left blank. The number of devices detected as being directly connected is set as the number of connected nodes. Further, the link information to the device generated for the directly connected device is set in the link to the node (S306).
The control system design support apparatus 1 completes the creation of the network configuration information 10 when all the devices are not connected to any more networks.

When the network configuration information 10 is generated by the above procedure, the system configuration information management unit 4 reflects the diagnosis result by the diagnosis processing unit 8 on the network configuration information 10 generated by the configuration management information management unit 5. Generate network status information.
When the diagnosis processing unit 8 determines that an abnormality has occurred in any device or transmission path, the system configuration information management unit 4 highlights the corresponding object in the network configuration information 10, for example. The network status information indicating the error message (the error message shown in the error information in FIG. 5) is generated and displayed on the information display unit 13.

(Diagnosis procedure)
Next, a procedure for automatic diagnosis of the network bus using the profile 20 will be described.
The control system design support apparatus 1 determines the order of diagnosis based on the generated network configuration information 10. Specifically, among (1) devices directly connected to the control system design support apparatus 1, (2) transmission line, (3) master station 32, and (4) devices directly connected to the transmission line (1) (5) Each device connected to the channel.
First, it is performed on the device main body directly connected to the control system design support apparatus 1. At this time, based on the diagnosis procedure described in the profile 20 corresponding to the device, the health of the device is diagnosed to determine normality / abnormality.
Second, the transmission path is diagnosed. In this embodiment, the profile 20 is assigned only to the device (Device), and the diagnosis procedure of the transmission path is described in the profile 20 of the directly connected device or the master station 32. In the CC-Link, the devices that can be directly connected to the control system design support apparatus 1 and the devices that can be the master station 32 are only the PLCs 31 and 32. However, the devices are not limited to the PLCs 31 and 32. If there is, the diagnosis procedure of the transmission path may be described in another device.
Up to this point, the process is performed in S202 / S203 of the ID information collection unit in FIG. This is because ID information cannot be collected via the network when there is an abnormality in the equipment directly connected to the control system design support apparatus 1 and the transmission path.
The third is for the master station 32 of the transmission path. For the device main body, the same processing as that of the device main body directly connected to the control system design support apparatus 1 is performed. In addition, since the master station 32 has a function of diagnosing the network from the standpoint of managing the network, the network diagnosis function is used to diagnose the health of the network and determine normality / abnormality. To do.
The fourth method is to diagnose the health of each device other than 1) among the devices directly connected to the transmission line based on the diagnostic procedure of each profile 20. For the slave station, in addition to looking at the network status area (including registers), the health of the device is confirmed by executing the diagnostic function for the device having the diagnostic function.
After all the devices directly connected to the transmission line have been diagnosed, the devices connected to the channel are also diagnosed based on the diagnostic procedure described in the corresponding profile 20.
The self-diagnosis is completed when the diagnosis is completed for all devices.

Hereinafter, the operation procedure of the diagnosis processing unit 8 is shown in FIG.
Upon receiving a diagnosis request from the ID information collection unit 6 or the configuration management information management unit 5, the diagnosis processing unit 8 sends the ID information 60 to the profile inquiry unit 7 in order to know the diagnosis procedure of the device or transmission path. And the user designation information 70 are passed and a search for the corresponding profile 20 is requested (S401).
Next, the diagnosis processing unit 8 acquires the number of test procedures from the diagnosis information of the profile 20 (S402). In the example of FIG. 5, it can be seen that there are seven procedures indicated by Number_of_TestSequences.
If the diagnostic information or the test procedure is not described in the profile, the diagnostic processing unit 8 ends without doing anything. If all the diagnosis indicated by the number of test procedures is completed, the process ends (S403).
The diagnosis processing unit 8 determines the type of processing to be performed by looking at the test type of the test procedure (TestSequence) (S404, S407, S411, S414).
When the test type is a status check (Yes in S404), the parameter specified by the parameter name in the test procedure description is compared with the content of the error information specified by the check range. Is determined (S405). If it is determined that there is an abnormality (No in S406), an error message defined by the error information is displayed (S416), and the diagnosis is terminated as an abnormality.
When the test type is command execution (Yes in S407), the command is executed by setting the value specified by the command code for the parameter specified by the parameter name in the description of the test procedure. (S408). Further, the contents of the parameter designated by the completion determination parameter name are periodically checked (S409), and the process waits until the value designated by the completion value is reached (S410).
When the test type is a diagnostic result check (Yes in S411), the parameter specified by the parameter name in the description of the test procedure is compared with the contents of all error information specified by the check range. Normal / abnormal is determined (S412). If it is determined that there is an abnormality (No in S413), an error message defined by the error information is displayed (S416), and the diagnosis is terminated as an abnormality.
When the test type is parameter setting (Yes in S414), the value specified by the setting value is set for the parameter specified by the parameter name in the description of the test procedure (S415).
The diagnosis processing unit 8 repeatedly performs the processing from S404 to S415 for the number of test procedures.

  As described above, according to the present embodiment, an operation that had to be performed individually for each device until now is connected to one PLC in the control system, thereby diagnosing each device. By confirming the health of the device and the transmission path using the profile describing the procedure, troublesome work can be reduced, and easy maintenance such as detection of an abnormality in the device or the transmission path or a simple connection error can be realized.

As described above, in the present embodiment, in the FA system constructed by connecting the physical switch that can be changed by the user and the device having the fixed device identification information inside to the transmission path,
Each device type has a profile that describes the attribute of the device and the diagnostic procedure for checking the health of the device and the transmission line.
By collecting ID information and user-specified information set by the user with physical switches from each device on the transmission path, the number of connected devices / connected devices are detected, and the connection relationship grasped from the detected contents is configured in the network. As information,
Collect the profiles for the devices connected to the transmission path while identifying the profile for the device by the combination of the detected device ID information and user-specified information,
The order of diagnosis is determined from the network configuration information, and in that order, the FA system configuration management and automatic diagnosis method for determining normality / abnormality and identifying the abnormal location are described based on the diagnostic procedure described in the corresponding profile.

  Further, in the present embodiment, the connection management is obtained from the device ID information and the user designation information, the network configuration is managed, and the FA system configuration management for determining the transmission path and the diagnosis order of the devices from the network configuration, and The automatic diagnosis method was explained.

  In this embodiment, the FA system configuration management and automatic diagnosis method in which a diagnostic procedure for confirming the health of the device and the transmission path is described in the profile prepared for each device type is described. did.

  For each device type, a profile that describes the diagnostic procedure for checking the health of the device and transmission path is prepared by combining the parameters (transmission path protocol version and the number of occupied stations) that can be set by the device. The FA system configuration management and automatic diagnosis method for specifying the corresponding profile using the device ID information and the user-specified information as keys have been described.

Embodiment 2. FIG.
The network configuration information 10 indicating the connection relation of devices stored in the local database of the control system design support apparatus 1 is filed, and the network configuration information file and the profile 20 group linked to the network configuration information 10 are collected. By storing in the USB memory, it can be expanded to the programmable display 40, and the programmable display 40 also realizes a diagnostic function similar to the engineering environment.

The programmable display device 40 diagnoses each device described in the network configuration information 10 file in the USB memory according to the diagnosis procedure described in the corresponding profile 20 so that the control system design support apparatus 1 Without it, the health of the device and the transmission path can be confirmed.
The processing flow of the programmable display 40 is basically the same as the processing flow of the engineering environment described in the first embodiment.
The programmable display 40 includes components other than the configuration management database 2 and the profile database 3 in the configuration shown in FIG. 1, and reads various profiles 20 and network configuration information 10 from a USB memory into a storage device. It has the same function as the control system design support apparatus 1 shown in the first embodiment.
That is, in the present embodiment, the programmable display 40 functions as a device management apparatus.
In addition, in FIG. 12, the structure which the programmable display 40 diagnoses an apparatus and a transmission path as an example is shown, and the apparatus which diagnoses an apparatus and a transmission path may be other than the programmable display 40.

  As described above, according to the present embodiment, by using the network configuration information file and the profile group associated with the device in the network configuration information file, the FA can be used without the control system design support device. The health of the device and the transmission path can be confirmed by a programmable display in the system.

  In the above description, the network of the control system such as the FA system has been described as a specific example of the communication network. However, the diagnostic methods described in the first and second embodiments connect, for example, in-vehicle devices to each other. The present invention can also be applied to device diagnosis in an in-vehicle network, an in-air network connecting aircraft-equipped devices, and a ship-in network connecting ship-equipped devices. It can also be applied to other types of networks.

As described above, in this embodiment, the network configuration information indicating the connection relationship of the devices stored in the control system design support apparatus is filed, and the network configuration information file and the profile group linked to the network configuration information are stored. By storing them together in a storage medium, you can develop them into programmable displays,
The programmable display unit diagnoses each device described in the network configuration information file according to the diagnosis procedure described in the corresponding profile, so that the device and transmission path can be controlled without a control system design support device. The FA system configuration management and automatic diagnosis method that can confirm the health were described.

Finally, hardware configuration examples of the control system design support apparatus 1 and the programmable display 40 shown in the first and second embodiments will be described.
FIG. 13 is a diagram illustrating an example of hardware resources of the control system design support apparatus 1 and the programmable display 40 shown in the first and second embodiments.
The configuration of FIG. 13 is merely an example of the hardware configuration of the control system design support apparatus 1 and the programmable display 40, and the hardware configuration of the control system design support apparatus 1 and the programmable display 40 is as shown in FIG. The configuration described above is not limited, and other configurations may be used.

In FIG. 13, the control system design support apparatus 1 and the programmable display device 40 include a CPU 911 (also referred to as a central processing unit, a central processing unit, a processing unit, an arithmetic unit, a microprocessor, a microcomputer, and a processor) that executes a program. Yes.
The CPU 911 is connected to, for example, a ROM (Read Only Memory) 913, a RAM (Random Access Memory) 914, a communication board 915, a display device 901, a keyboard 902, a mouse 903, and a magnetic disk device 920 via a bus 912. Control hardware devices.
Further, the CPU 911 may be connected to an FDD 904 (Flexible Disk Drive), a compact disk device 905 (CDD), a printer device 906, and a scanner device 907. Further, instead of the magnetic disk device 920, a storage device such as an optical disk device or a memory card (registered trademark) read / write device may be used.
The RAM 914 is an example of a volatile memory. The storage media of the ROM 913, the FDD 904, the CDD 905, and the magnetic disk device 920 are an example of a nonvolatile memory. These are examples of the storage device.
A communication board 915, a keyboard 902, a mouse 903, a scanner device 907, an FDD 904, and the like are examples of input devices.
The communication board 915, the display device 901, the printer device 906, and the like are examples of output devices.

  As shown in FIG. 2, the communication board 915 is connected to a network. For example, the communication board 915 may be connected to a LAN (local area network), the Internet, a WAN (wide area network), or the like.

The magnetic disk device 920 stores an operating system 921 (OS), a window system 922, a program group 923, and a file group 924.
The programs in the program group 923 are executed by the CPU 911 using the operating system 921 and the window system 922.

The RAM 914 temporarily stores at least part of the operating system 921 program and application programs to be executed by the CPU 911.
The RAM 914 stores various data necessary for processing by the CPU 911.

The ROM 913 stores a BIOS (Basic Input Output System) program, and the magnetic disk device 920 stores a boot program.
When the control system design support apparatus 1 and the programmable display 40 are activated, the BIOS program in the ROM 913 and the boot program in the magnetic disk device 920 are executed, and the operating system 921 is activated by the BIOS program and the boot program.

  The program group 923 stores programs for executing the functions described as “˜units” in the description of the first and second embodiments. The program is read and executed by the CPU 911.

In the description of the first and second embodiments, the file group 924 includes “determination of”, “diagnosis of”, “collection of”, “search of”, “calculation of”, and “comparison of”. , Information, data, signal values, variable values, and parameters indicating the results of the processing described as “update of”, “setting of”, “registration of”, “selection of”, etc. It is stored as each item of “file” and “˜database”.
The “˜file” and “˜database” are stored in a recording medium such as a disk or a memory. Information, data, signal values, variable values, and parameters stored in a storage medium such as a disk or memory are read out to the main memory or cache memory by the CPU 911 via a read / write circuit, and extracted, searched, referenced, compared, and calculated. Used for CPU operations such as calculation, processing, editing, output, printing, and display.
Information, data, signal values, variable values, and parameters are stored in the main memory, registers, cache memory, and buffers during the CPU operations of extraction, search, reference, comparison, calculation, processing, editing, output, printing, and display. It is temporarily stored in a memory or the like.
The arrows in the flowcharts described in the first and second embodiments mainly indicate input / output of data and signals. The data and signal values are the memory of the RAM 914, the flexible disk of the FDD904, the compact disk of the CDD905, and the magnetic field. Recording is performed on a recording medium such as a magnetic disk of the disk device 920, other optical disks, mini disks, DVDs, and the like. Data and signals are transmitted online via a bus 912, signal lines, cables, or other transmission media.

  In addition, what is described as “˜unit” in the description of the first and second embodiments may be “˜circuit”, “˜device”, “˜device”, and “˜step”, It may be “˜procedure” or “˜processing”. That is, what is described as “˜unit” may be realized by firmware stored in the ROM 913. Alternatively, it may be implemented only by software, or only by hardware such as elements, devices, substrates, and wirings, by a combination of software and hardware, or by a combination of firmware. Firmware and software are stored as programs in a recording medium such as a magnetic disk, a flexible disk, an optical disk, a compact disk, a mini disk, and a DVD. The program is read by the CPU 911 and executed by the CPU 911. That is, the program causes the computer to function as the “˜unit” in the first and second embodiments. Alternatively, the computer executes the procedure and method of “to unit” in the first and second embodiments.

  As described above, the control system design support apparatus 1 and the programmable display 40 shown in the first and second embodiments include a CPU as a processing device, a memory as a storage device, a magnetic disk, a keyboard as an input device, a mouse, a communication board, and the like. The computer includes a display device, a communication board, and the like as an output device, and implements the functions indicated as “˜units” using the processing device, the storage device, the input device, and the output device as described above.

FIG. 3 is a diagram illustrating a configuration example of a control system design support apparatus according to the first embodiment. FIG. 2 is a diagram illustrating a configuration example of a control system according to the first embodiment. FIG. 4 is a diagram illustrating an example of ID information according to the first embodiment. FIG. 3 is a diagram showing an example of network configuration information according to the first embodiment. FIG. 3 is a diagram illustrating an example of a profile according to the first embodiment. FIG. 4 is a diagram showing an example of user designation information according to the first embodiment. The figure which shows the example of the collection procedure of ID information which concerns on Embodiment 1, and user designation information. FIG. 3 is a flowchart showing an operation example of the control system design support apparatus according to the first embodiment. FIG. 3 is a flowchart showing an operation example of the control system design support apparatus according to the first embodiment. FIG. 3 is a flowchart showing an operation example of the control system design support apparatus according to the first embodiment. FIG. 3 is a flowchart showing an operation example of the control system design support apparatus according to the first embodiment. FIG. 4 is a diagram illustrating an example of a system configuration according to a second embodiment. The figure which shows the hardware structural example of the control system design support apparatus and programmable display which concern on Embodiment 1,2.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 1 Control system design support apparatus, 2 Configuration management database, 3 Profile database, 4 System configuration information management part, 5 Configuration management information management part, 6 ID information collection part, 7 Profile inquiry part, 8 Diagnosis processing part, 10 Network configuration information , 11 system components, 12 user instruction input unit, 13 information display unit, 20 profile, 40 programmable display.

Claims (9)

  1. A device management device that manages multiple types of devices connected to a managed network,
    For each device type, a profile information storage unit that stores profile information in which a diagnosis procedure for diagnosing the state of the device is described;
    An information collection unit for receiving notification information for notifying the device type of each device connected to the managed network;
    A diagnostic processing unit for acquiring corresponding profile information based on the device type notified in the notification information received by the information collecting unit, and diagnosing the status of each device according to a diagnostic procedure using the acquired profile information; Have
    The profile information storage unit
    For each device type, it stores profile information that describes whether there is a possibility that a lower device is connected to the device,
    The information collecting unit
    When the notification information for any device is received, the profile information corresponding to the device type of the device is examined to determine whether there is a possibility that a lower device is connected to the device. If it is determined that there is a possibility that a lower-level device is connected, investigate whether or not a lower-level device is connected to the device, and if a lower-level device is connected to the device, A device management apparatus that receives notification information that notifies a device type of a lower device.
  2. The diagnosis processing unit
    When diagnosing the state of a specific device among devices connected to the managed network, the state of the specific device is diagnosed and the state of a transmission path in the managed network is diagnosed. The device management apparatus according to claim 1.
  3. The diagnosis processing unit
    When diagnosing the state of the device to be diagnosed first among the devices connected to the managed network, diagnose the state of the transmission path in the managed network,
    The device management apparatus according to claim 2, wherein when a state of a transmission path in the management target network is normal, a state of another device connected to the management target network is diagnosed.
  4. The device management apparatus further includes:
    A configuration information generation unit that analyzes the notification information received by the information collection unit and generates network configuration information indicating a connection relationship of a plurality of types of devices connected to the management target network;
    Each device shown in the network configuration information generated by the configuration information generation unit is associated with a diagnosis result by the diagnosis processing unit, and indicates a connection relationship of a plurality of types of devices connected to the management target network. The device management apparatus according to claim 1, further comprising: a state information generation unit that generates network state information indicating a diagnosis result for the device.
  5. The profile information storage unit
    Stores profile information for each device type and for each user-defined attribute defined for each device by a user using the device management apparatus,
    The information collecting unit
    Receiving notification information for notifying the device type and user-defined attribute of each device connected to the managed network;
    The diagnosis processing unit
    The corresponding profile information is acquired based on the device type and user-defined attribute notified in the notification information received by the information collection unit, and the status of each device is diagnosed according to the diagnostic procedure using the acquired profile information. The device management apparatus according to any one of claims 1 to 4, wherein
  6. The information collecting unit
    The notification information of the slave station device managed by the master station device is received from a master station device that manages two or more devices connected to the management target network as slave station devices. The apparatus management apparatus in any one of -5.
  7. The device management apparatus
    As the managed network, FA (Factory Automation) intended for network systems, to any one of claims 1 to 6, characterized in that managing the plurality of types of devices connected to the network of the FA system The device management apparatus described.
  8. A device management method for managing a plurality of types of devices connected to a managed network by a computer,
    An information collecting step for receiving notification information for notifying a device type of each device connected to the managed network;
    Based on the device type notified in the notification information received by the information collecting step from the profile information storage area storing the profile information in which the diagnosis procedure for diagnosing the state of the device is described for each device type A profile information acquisition step for acquiring corresponding profile information;
    A diagnostic processing step of diagnosing the state of each device according to a diagnostic procedure using the profile information acquired by the profile information acquisition step ;
    In the profile information acquisition step,
    The computer
    For each device type, obtain profile information that describes whether there is a possibility that a lower device is connected to the device,
    In the information collecting step,
    The computer
    When the notification information for any device is received, the profile information corresponding to the device type of the device is examined to determine whether there is a possibility that a lower device is connected to the device. If it is determined that there is a possibility that a lower-level device is connected, investigate whether or not a lower-level device is connected to the device, and if a lower-level device is connected to the device, A device management method comprising receiving notification information for notifying a device type of a lower device .
  9. To a computer that manages multiple types of devices connected to the managed network,
    Information collection processing for receiving notification information for notifying the device type of each device connected to the managed network;
    Based on the device type notified in the notification information received by the information collection process from the profile information storage area storing the profile information describing the diagnostic procedure for diagnosing the state of the device for each device type Profile information acquisition processing for acquiring corresponding profile information;
    Using the profile information acquired by the profile information acquisition process, a program for executing a diagnosis process for diagnosing the state of each device according to a diagnosis procedure ,
    In the profile information acquisition process,
    In the computer,
    For each device type, get the profile information that describes whether there is a possibility that a lower device is connected to the device,
    In the information collection process,
    In the computer,
    When the notification information for any device is received, the profile information corresponding to the device type of the device is inspected to determine whether there is a possibility that a lower device is connected to the device. If it is determined that there is a possibility that a lower-level device is connected, check whether the lower-level device is connected to the device, and if the lower-level device is connected to the device, A program for receiving notification information for notifying the device type of the lower device .
JP2008116500A 2008-04-26 2008-04-26 Device management apparatus, device management method, and program Active JP5030852B2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
JP2008116500A JP5030852B2 (en) 2008-04-26 2008-04-26 Device management apparatus, device management method, and program

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
JP2008116500A JP5030852B2 (en) 2008-04-26 2008-04-26 Device management apparatus, device management method, and program

Publications (2)

Publication Number Publication Date
JP2009266047A JP2009266047A (en) 2009-11-12
JP5030852B2 true JP5030852B2 (en) 2012-09-19

Family

ID=41391801

Family Applications (1)

Application Number Title Priority Date Filing Date
JP2008116500A Active JP5030852B2 (en) 2008-04-26 2008-04-26 Device management apparatus, device management method, and program

Country Status (1)

Country Link
JP (1) JP5030852B2 (en)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP5458968B2 (en) * 2010-03-08 2014-04-02 富士電機株式会社 Safety control system
JP2014016753A (en) * 2012-07-09 2014-01-30 Mitsubishi Electric Corp Setting support system
JP6021552B2 (en) * 2012-09-27 2016-11-09 株式会社日立システムズ Monitoring device, monitoring system, program, and monitoring method
JP6235259B2 (en) * 2013-07-17 2017-11-22 株式会社日立製作所 Communication control device, communication control method, and communication control system
US10018998B2 (en) * 2014-02-14 2018-07-10 Yokogawa Electric Corporation Field device commissioning system and field device commissioning method
US9719887B2 (en) * 2014-02-14 2017-08-01 Yokogawa Electric Corporation Field device commissioning system and field device commissioning method
JP6550733B2 (en) 2014-12-01 2019-07-31 富士通株式会社 Information processing apparatus, diagnostic method, and diagnostic program
JP6413990B2 (en) * 2015-09-11 2018-10-31 株式会社安川電機 Servo controller parameter adjusting device, servo system and computer program
JP6109447B1 (en) * 2016-04-06 2017-04-05 三菱電機株式会社 Information processing method and information processing apparatus

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5980078A (en) * 1997-02-14 1999-11-09 Fisher-Rosemount Systems, Inc. Process control system including automatic sensing and automatic configuration of devices
JP2002268730A (en) * 2001-03-09 2002-09-20 Mitsubishi Electric Corp Maintenance system for field device
JP2004234330A (en) * 2003-01-30 2004-08-19 Toshiba Corp Information processor and network connection diagnostic method
JP2006085612A (en) * 2004-09-17 2006-03-30 Fuji Xerox Co Ltd Operation diagnosing device, its method, and its program
JP2007249312A (en) * 2006-03-14 2007-09-27 Yokogawa Electric Corp Field equipment management device and method

Also Published As

Publication number Publication date
JP2009266047A (en) 2009-11-12

Similar Documents

Publication Publication Date Title
JP5936180B2 (en) Process control system
KR101105498B1 (en) Configurable plc and scada-based control system
US7983892B2 (en) System and method for accessing and presenting health information for field devices in a process control system
US9483035B2 (en) Method for integrating at least one field device into a network of automation technology
EP1586966A2 (en) Control system configuration device
US20080040477A1 (en) Methods and apparatus for control using control devices that provide a virtual machine environment and that communicate via an ip network
EP1401171B1 (en) Electronic apparatus for a bussystem
US20050010307A1 (en) Tool for configuring and managing a process control network including the use of spatial information
US7117049B2 (en) Industrial controller based on distributable technology objects
KR940002324B1 (en) Programmable controller
DE102008055660B4 (en) Method and device for accessing a functional module of an automation system
US7043316B2 (en) Location based programming and data management in an automated environment
CN101460909B (en) System management human-machine interface
JP2012084162A5 (en)
JP5841643B2 (en) Method and apparatus for creating process control graphics based on process control algorithm information
US7600234B2 (en) Method for launching applications
US20130123951A1 (en) Systems and methods for error detection and diagnostics visualization
US8321790B2 (en) System management user interface providing user access to status information for process control system equipment including a search function
DE102004051179B4 (en) Control system adjustment device, method of adjusting a control system, and adjustment program
JP6549748B2 (en) Process control configuration method, process control configuration system, and software system
JP2014116027A5 (en)
US8543741B2 (en) Network scanning and management in a device type manager of type device
JP6190334B2 (en) Method, product, apparatus, and configuration system for configuring alarm response
JP5154875B2 (en) Process control system including flexible input / output device, method, and machine accessible medium storing program
US20070240052A1 (en) System management user interface providing user access to status information for process control system equipment including a status monitor

Legal Events

Date Code Title Description
A621 Written request for application examination

Free format text: JAPANESE INTERMEDIATE CODE: A621

Effective date: 20101226

A977 Report on retrieval

Free format text: JAPANESE INTERMEDIATE CODE: A971007

Effective date: 20120111

A131 Notification of reasons for refusal

Free format text: JAPANESE INTERMEDIATE CODE: A131

Effective date: 20120117

A521 Written amendment

Free format text: JAPANESE INTERMEDIATE CODE: A523

Effective date: 20120209

TRDD Decision of grant or rejection written
A01 Written decision to grant a patent or to grant a registration (utility model)

Free format text: JAPANESE INTERMEDIATE CODE: A01

Effective date: 20120529

A01 Written decision to grant a patent or to grant a registration (utility model)

Free format text: JAPANESE INTERMEDIATE CODE: A01

A61 First payment of annual fees (during grant procedure)

Free format text: JAPANESE INTERMEDIATE CODE: A61

Effective date: 20120626

R150 Certificate of patent or registration of utility model

Free format text: JAPANESE INTERMEDIATE CODE: R150

FPAY Renewal fee payment (event date is renewal date of database)

Free format text: PAYMENT UNTIL: 20150706

Year of fee payment: 3

R250 Receipt of annual fees

Free format text: JAPANESE INTERMEDIATE CODE: R250

R250 Receipt of annual fees

Free format text: JAPANESE INTERMEDIATE CODE: R250

R250 Receipt of annual fees

Free format text: JAPANESE INTERMEDIATE CODE: R250

R250 Receipt of annual fees

Free format text: JAPANESE INTERMEDIATE CODE: R250

R250 Receipt of annual fees

Free format text: JAPANESE INTERMEDIATE CODE: R250