JP4879926B2 - Diagnostic system, method and program for network system - Google Patents

Description

  The present invention relates to a network system diagnosis system, method, and program suitable for monitoring and diagnosing a process control system in, for example, the steel industry.

  In process control systems in the steel industry, etc., where high reliability is required for 24-hour operation, computers and networks dedicated to heavy electrical manufacturers have been used so far, but there have been difficulties in terms of cost reduction and expandability.

  Therefore, in recent years, specifications have been released, and the introduction of open systems using general-purpose products is progressing. However, the scale of application increases, and the number and combination of general-purpose products becomes enormous when the needs to realize a high-functional system applying the latest IT technology from the operation department are met. In particular, particularly in the case of a network, the influence of a failure that has occurred in a part affects the entire system, and the phenomenon is irregular and non-reproducible, which increases the difficulty of investigating the cause of the failure and recovery work.

  Further, as the introduction of open systems progresses, there will be cases where transmission is required with devices that cannot be directly connected to the open system network among existing computers dedicated to heavy electrical equipment manufacturers. For this reason, for example, the number of system configurations in which protocol converters that convert standard / representative communication protocol TCP / IP to individual-specific serial transmission communication protocols (other communication protocols) are installed between the network and existing devices has increased. is doing.

  It is unrealistic for network specialists who require advanced expertise to wait 24 hours in a distributed process control system because the work is huge and unrealistic. Attempts were also made to introduce dedicated systems and tools to monitor and diagnose the system. However, monitoring and diagnosis of the process control system should be performed while grasping the status of facilities that are limited by ITV, hearing the operation of the site operator at each site in the manufacturing process that is not on the computer, and the operation status. Is essential.

JP-A-8-8998

  Operators working 24 hours on site and workers in maintenance departments who are waiting for the maintenance of the entire facility, while looking at the situation at the site, do not require advanced network expertise. There was no inexpensive, versatile and easy-to-use tool that could flexibly monitor and diagnose complex process control systems. In particular, when a protocol converter is installed, monitoring / diagnosis only on the TCP / IP side is not sufficient for investigating the cause and recovery work when a failure occurs, and monitoring / diagnosis including other communication protocols is necessary. An inexpensive, versatile, and easy-to-use tool that allows maintenance workers to flexibly monitor and diagnose while looking at the situation in the field without requiring advanced network expertise was desired.

  As a technique related to a communication protocol, for example, Patent Document 1 discloses a communication protocol failure analysis apparatus. However, the technique disclosed in Patent Document 1 performs failure analysis by designating a communication protocol, and does not monitor or diagnose transmission using a different communication protocol via a protocol converter.

  The present invention has been made in view of the above points. In a network system in which a protocol converter is introduced, advanced network expertise is not required, and monitoring and diagnosis between different communication protocols can be efficiently performed. It aims to be able to do it.

In the network system diagnosis system of the present invention, a network configured by connecting a plurality of devices and a communication target device performing data communication using a communication protocol different from the communication protocol of the network are connected via a protocol converter A network system diagnosis system for monitoring and diagnosing the network system, the first collection means for collecting data on the network, and the second collection means for collecting data transmitted and received by the communication target device; The data on the network collected by the first collecting means is searched for data corresponding to the data transmitted and received by the communication target device collected by the second collecting means on the basis of time, and the table is calculated And a transmission diagnosis means for outputting to a sheet created by software.
In the network system diagnosis method of the present invention, a network configured by connecting a plurality of devices and a communication target device performing data communication using a communication protocol different from the communication protocol of the network are connected via a protocol converter A network system diagnosis method for monitoring and diagnosing a network system, comprising: a procedure for collecting data on the network; a procedure for collecting data transmitted and received by the communication target device; and a method for collecting the data on the collected network And searching the data corresponding to the data transmitted / received by the communication target device among the collected data on the basis of time, and outputting the result to a sheet created by spreadsheet software.
A program of the present invention is a network system in which a network configured by connecting a plurality of devices and a communication target device that performs data communication using a communication protocol different from the communication protocol of the network are connected via a protocol converter. Is a program for causing a computer to execute processing for monitoring and diagnosing data, processing for collecting data on the network, processing for collecting data transmitted and received by the communication target device, and processing on the collected network Among the data, a process corresponding to the collected data to be transmitted / received by the communication target device is searched based on time, and a process of outputting to a sheet created by spreadsheet software is executed by a computer.

  According to the present invention, in a network system in which a protocol converter is introduced, data on one communication protocol side and data on the other communication protocol side are automatically associated with each other on the basis of time. It does not require network expertise and can efficiently monitor and diagnose between different communication protocols. As a result, even on-site workers who are not network specialists can easily monitor and diagnose the network system flexibly while grasping the situation of the site. Furthermore, since the data is output to a sheet created by spreadsheet software, it is inexpensive and versatile, and can be easily applied to a plurality of distributed network systems.

Preferred embodiments of the present invention will be described below with reference to the accompanying drawings.
FIG. 1 shows a configuration example of a process control system including a diagnosis system to which the present invention is applied. A plurality of switching hubs 200 are connected to the control server 100 that controls the entire process. In FIG. 1, the control server 100 is illustrated as a single device, but may be configured by a plurality of devices.

  The switching hub 200 is installed for each system such as a manufacturing process control system, an HMI (Human Machine Interface) system, and an upper system that supervises the manufacturing process control system. A plurality of network devices 300 such as sensors, personal computers, and hubs are connected. These control server 100, switching hub 200, and network device 300 constitute a TCP / IP network NW.

  In addition, a communication target device 400 that is an existing device is connected to a predetermined switching hub 200 via a protocol converter (protocol converter) 500 and a modem. The protocol converter 500 converts the communication protocol (TCP / IP) of the TCP / IP network NW to the serial transmission communication protocol of the individual specification of the communication target device 400.

  A diagnostic device 1 for monitoring and diagnosing the process control system is connected to these switching hubs 200 via the switching hub 2. In the present embodiment, the diagnostic device 1 functions as a transmission diagnostic means in the present invention.

  A serial transmission capture device 700 is connected between the protocol converter 500 and the communication target device 400 via the branch cable 600. The serial transmission capture device 700 collects data transmitted / received by the communication target device 400 and associates time information with the capture data and stores it in the capture data storage unit 800. In addition, the serial transmission capture device 700 transmits the capture data stored in the capture data storage unit 800 to the diagnostic device 1. In the present embodiment, the serial transmission capture device 700 functions as the second collection means referred to in the present invention.

  As will be described in detail below, the diagnostic system including the diagnostic device 1 and the serial transmission capture device 700 as the main components includes (1) a ping issue monitoring tool, (2) a CRC error monitoring tool, and (3) a packet. It functions as a capture tool and (4) a serial transmission diagnostic tool.

(Functional configuration of diagnostic device 1)
FIG. 2 shows a functional configuration of the diagnostic apparatus 1. Reference numeral 11 denotes a display device. Reference numeral 12 denotes an input device such as a keyboard or a pointing device.

  A worksheet storage unit 13 stores a worksheet created by spreadsheet software (for example, Excel (registered trademark)). As the worksheet, common definition sheet 13a, execution schedule sheet 13b, network configuration diagram sheet 13c, network definition sheet 13d, ping result sheet 13e, ping log sheet 13f, SW list sheet 13g, SW monitoring log sheet 13h, serial transmission diagnosis A result sheet 13i and a serial transmission diagnosis log sheet 13j are created.

  A ping issuing unit 14 transmits a response request to a device on the process control system based on the network definition sheet 13d (ping issuance). Note that ping is generally the most basic command used in a TCP / IP network to check whether an IP packet has reached a destination or is reachable in IP.

  Reference numeral 15 denotes a diagnosis unit that monitors and diagnoses the process control system. The diagnosis unit 15 diagnoses the state of each device based on the response from each device on the process control system to the ping issuance by the ping issuing unit 14. In this embodiment, not only the presence / absence of a response but also the time until the response is returned is checked. Then, the diagnosis result is output to the ping result sheet 13e. The diagnosis unit 15 diagnoses data on the TCP / IP network NW and data transmitted / received by the communication target device 400 (that is, capture data collected by the serial transmission capture device 700) in time series. Then, the diagnosis result is output to the serial transmission diagnosis result sheet 13i.

  Reference numeral 16 denotes a display control unit that displays a ping result sheet 13e, a serial transmission diagnosis result sheet 13i, and the like on the display device 11, and reflects the diagnosis result by the diagnosis unit 15 on the network configuration diagram sheet 13c and displays it on the display device 11. To do. For example, on the network configuration diagram sheet 13c, a device that does not respond or a device that detected a transmission error is displayed in red, and a device that responds slowly is displayed in yellow.

  Reference numeral 17 denotes a CRC (Cyclic Redundancy Check) error monitoring unit that performs CRC error monitoring based on the SW list sheet 13g. CRC is called cyclic redundancy check, and is one of error detection / correction methods for checking whether data is correctly transmitted by data transmission or the like. On the process control system, there are devices for accumulating the number of occurrences of CRC errors, for example, switching hubs 200 for each system, and the number of occurrences of CRC errors that are a precursor of trouble is collected from these devices.

  A log output unit 18 outputs a log to the ping log sheet 13f when the result of ping issue monitoring is NG, and logs to the SW monitoring log sheet 13h when a CRC error occurs during CRC error monitoring. When a serial transmission error is detected, a serial transmission diagnostic log sheet 13j is output.

  Reference numeral 19 denotes a capture unit that collects data (packets) on the TCP / IP network NW via the switching hubs 200 of each system, and associates and stores time information. In the present embodiment, the capture unit 19 functions as the first collection means referred to in the present invention.

  Reference numeral 20 denotes a serial transmission data acquisition unit that acquires capture data stored in the capture data storage unit 800 from the serial transmission capture device 700.

  Note that the monitoring device 1 may be configured by a plurality of devices or a single device. For example, (1) a ping issue monitoring tool and (2) a personal computer functioning as a CRC error monitoring tool, and (3) a packet capture tool and (4) a personal computer functioning as a serial transmission diagnostic tool may be configured separately. Good. In FIG. 1, the monitoring device 1 and the serial transmission capture device 700 are illustrated as separate bodies, but may be integrated.

(worksheet)
As shown in FIG. 3, the common definition sheet 13a is used to set a ping issue default designation, a diagnosis execution mode, setting parameters for serial transmission diagnosis, and a batch file when an error occurs. Specifically, as partly shown in Table 1 below, the number of ping repetitions, execution interval, block size, timeout, TTL, execution mode, data from-to (transmission, reception), timeout, scan time, Set the execution file name (path, batch file, startup count limit) when an error occurs. The timeout is a time for setting an allowable time difference of data transmission / reception between the TCP / IP network NW and the communication target device 400 in the serial transmission diagnosis. The scan time is a time set for searching TCP / IP data corresponding to serial transmission data in serial transmission diagnosis.

  As shown in FIG. 4, the execution schedule sheet 13b is for designating an execution schedule for ping issue monitoring, CRC error monitoring, and serial transmission diagnosis. Specifically, as shown in Table 2 below, the execution cycle, execution day, start interval, start time, and execution mode are set. Also, whether the schedule is currently being executed or stopped is displayed.

  The network configuration diagram sheet 13c is a diagram showing the configuration of the process control system as shown in FIG. As described above, the display control unit 16 displays the corresponding device on the network configuration diagram sheet 13c by enclosing the color corresponding to the diagnosis result by the diagnosis unit 15, so that the portion to be discolored is surrounded by the cell combination. Leave in. The network configuration diagram sheet 13c is always created at the design stage of the process control system and is also used at the maintenance operation stage, and is taken in for network monitoring. In the example of FIG. 5, the marker for marking the steel plate corresponds to the communication target device 400 shown in FIG.

  As shown in FIG. 6, the network definition sheet 13d has network information (host name, IP address, connected device code) and device information (device type, manufacturer, model name) for each device set in the network configuration diagram sheet 13c. And so on. Specifically, as shown in Table 3 below, the connection number, device code, network information, device information, design information (row, column), installation location, size, and timeout are set. As described above, the ping issuing unit 14 transmits a response request to the device on the process control system based on the network definition sheet 13d.

  As shown in FIG. 7, the ping result sheet 13e is for outputting the result of ping issuance monitoring, and displays not only the NG count and OK count but also the success rate. As described above, the diagnosis unit 15 outputs a diagnosis result to the ping result sheet 13e.

  Although not specifically illustrated, the ping log sheet 13f outputs a log when the result of ping issue monitoring is NG, and sets the items of the result, date, target, IP address, status, and remarks. . As described above, when the result of ping issue monitoring is NG, the log output unit 18 outputs a log to this ping log sheet 13f.

  The SW list sheet 13g is for setting switching hub information for monitoring a CRC error, as shown in FIG. Specifically, the CRC error monitoring period is set, and the IP address of each switching hub and the row and column of the switching hub arranged in the network configuration diagram sheet 13c are set. Also, an object ID in which the number of CRC errors is stored is set.

  Although not specifically shown, the SW monitoring log sheet 13h is for outputting a log when a CRC error occurs during CRC error monitoring. As described above, when a CRC error occurs during CRC error monitoring, the log output unit 18 outputs a log to the SW monitoring log sheet 13h.

  The serial transmission diagnosis result sheet 13i is for outputting the result of the serial transmission diagnosis as shown in FIG. Year / month / day, hour / minute / second, microsecond, transmission / reception side IP address, dump, and the like are displayed. As described above, the diagnosis unit 15 outputs a diagnosis result to the serial transmission diagnosis result sheet 13i.

  As shown in FIG. 10, the serial transmission diagnosis log sheet 13j outputs a log when the result of serial transmission diagnosis is NG. The result, date, target, IP address, status, size, timeout, Set the remark items. As described above, if the result of the serial transmission diagnosis is NG, the log output unit 18 outputs a log to the serial transmission diagnosis log sheet 13j.

((1) PING issue monitoring tool)
When a command button (not shown) is operated on the display device 11, a ping issue operation screen 1100 is displayed on the display device 11, as shown in FIG. In the ping issue operation screen 1100, reference numeral 1101 denotes a selection button for selecting whether to execute “all node diagnosis (infinite)”, “all node diagnosis (schedule)”, or “all node diagnosis (once)”. . Reference numeral 1102 denotes a diagnosis stop button for instructing to stop diagnosis. Reference numeral 1103 denotes a setting field for setting a device code when performing a trace route search. Here, the trace route is a path of a node for returning a response at the time of executing ping. Reference numeral 1104 denotes a search start button for instructing start of trace route search. Reference numeral 1105 denotes a ping button for instructing execution of ping when performing a trace route search. Reference numeral 1106 denotes a button for referring to the ping result sheet 13e. Further, the ping issue operation screen 1100 indicates that the initial state is white, the ping issuance is blue, the abnormality (no response) is red, and the unstable (slow response) is yellow. .

  FIG. 12 shows the flow of the ping issue process. First, the data of the network definition sheet 13d is acquired (step S1201). Next, the device code of the own terminal is acquired based on the network definition sheet 13d (step S1202). If the device code of the own terminal cannot be acquired, an error message is output, and then the process ends. Next, all combinations of the own terminal and other terminals are acquired based on the network definition sheet 13d (step S1203). Next, if the search start button 1104 and the PING button 1105 are pressed, each process is executed (step S1204 (see FIG. 14), S1205 (see FIG. 15)). If the search is not a trace route search, the processes of steps S1204 and S1205 are repeated for the number of acquisitions without pressing the search start button 1104 and the PING button 1105. Then, the PING result is reflected on the network configuration diagram sheet 13c and displayed, and a PING log sheet 13f is created (step S1206).

  When the “all node diagnosis (one time)” button is pressed among the selection buttons 1101 on the ping issue operation screen 1100, if the execution mode set in the common definition sheet 13a is PING or both, FIG. As shown, a PING issue process is executed (step S1301 (see FIG. 12)). Further, when the execution mode set in the common definition sheet 13a is CRC or both, the CRC error accumulation is acquired (step S1302).

  When the “all node diagnosis (infinite)” button among the selection buttons 1101 on the ping issue operation screen 1100 is pressed, the processing of FIG. 13 is repeated until the diagnosis stop button 1102 is pressed.

  When the “all node diagnosis (schedule)” button among the selection buttons 1101 on the ping issue operation screen 1100 is pressed, the schedule is set according to the schedule set in the execution schedule sheet 13b until the diagnosis stop button 1102 is pressed. Repeat the process.

  FIG. 14 shows processing when the search start button 1104 is pressed in step S1204. When the search start button 1104 is pressed, a trace route search of the ping issue destination device code is performed from the input ping issue source device code. First, it is checked whether the device code set in the setting field 1103 of the ping issue operation screen 1100 is set in the internal information of the network configuration diagram sheet 13c, and whether the device code input to the issuer device code is the local terminal. Is checked (step S1401). Next, a trace route from the ping issuing source device code to the ping issuing destination device code is acquired from the internal information (step S1401).

  FIG. 15 shows processing when the ping button 1105 is pressed in step S1205. When the ping button 1105 is pressed, a ping is issued between the trace routes acquired by the processing when the search start button 1104 is pressed. First, the trace route of the ping issue destination is output from the ping issue source acquired by the processing when the search start button 1104 is pressed to the search route of the ping result sheet 13e (step S1501). Next, an IP address is acquired from the ping issue destination device code from the internal information (step S1502). Next, a ping is issued to the IP address acquired in step S1502 (step S1503). Next, the network configuration diagram sheet 13c is displayed based on the output result, and if it is NG, a log is output to the ping log sheet 13f (step S1504).

((2) CRC error monitoring tool)
When a command button (not shown) is operated on the display device 11, an SNMP SW monitoring screen 804 is displayed on the display device 11 together with the SW list sheet 13g as shown in FIG. The SNMP SW monitoring screen 804 displays a list of devices that accumulate the number of CRC error occurrences set in the SW list sheet 13g.

  When the CRC error number acquisition button 801 is pressed, the number of CRC errors (counter total value) in the SW list sheet 13g is updated. When the CRC error monitoring button 802 is pressed, the network configuration diagram sheet 13c is displayed, and CRC error monitoring is started every monitoring period. If a CRC error is detected during CRC error monitoring, a log is output to the SW monitoring log sheet 13h. When the monitoring stop button 803 is pressed, CRC error monitoring is stopped.

((3) Packet capture tool)
The capture unit 19 extracts, outputs, and analyzes a message that matches a specified condition using data obtained by capturing a packet on the TCP / IP network NW. For the analysis, Ethereal can be used, and Excel analysis is also possible. In the analysis by Excel, the result converted into the csv format can be read and displayed. As a linkage function, the analysis result can be output in the message trace tool format.

  First, the capture method will be described. In the capture setting screen 1600 shown in FIG. 16, the network adapter 1601 used for capture is selected in the setting field 1601. Next, the IP address and port number of the transmission source / destination are designated in the setting column 1602. In this case, if "*" is specified, it is executed for all values. In the setting field 1603, the communication protocol (TCP, UDP, all) to be captured is selected. Next, “capture” is selected with the radio button 1604. Next, the save destination of the capture result is designated in the setting field 1605. Thereafter, when a capture execution button 1606 is pressed, capture is executed. To stop the capture, a capture stop button 1607 is pressed.

  Next, an analysis setting method will be described. As shown in FIG. 17, when “Analyze Excel” is selected with the radio button 1604, the screen changes according to the setting as described below. To start the analysis, the analysis button 1608 is pressed after setting each condition.

  When a communication protocol is selected in the setting field 1603, a message type list 1609 is displayed as shown in FIG. Therefore, when a message type (Csemi standard transmission, Csemi PIO transmission) is selected, a filter condition setting field 1610 is displayed. FIG. 17 shows a state in which a filter condition setting field 1610 is displayed when Csemi standard transmission is selected. Csemi is an abbreviation for “NS SEMI SYSTEM (registered trademark)” and is an application that serves as a bridge between application software for process control and general-purpose software Windows (registered trademark) NT (registered trademark). It is a middleware for human control. With regard to Csemi, the technology is disclosed in Nippon Steel Technical Bulletin No363 1997 and Nippon Steel Technical Bulletin No379 2003 by the present applicant.

  In this embodiment, in the case of “Csemi standard transmission” of the communication protocol “TCP”, as shown in FIG. 17, in the output setting column 1611, the output setting (record size, binary) for the message trace tool binary file (.bin). Logical line No., number of records, transmission / reception type).

  Further, as shown in FIG. 17, an Excel analysis setting field 1612 becomes valid, and options for analysis are designated there. Here, you can select the capture date and time, the analysis method, and the output format. In other words, the capture date and time (start point) and the capture date and time (end point) are designated (beginning and end points of automatic merging). In addition to selecting whether to start automatically or not, the software to be used for analysis is specified. Select the check box to output a dump of the data part when outputting the csv file. In the setting field 1605, the name of the target file to be searched is specified. If the beginning of the file name matches, it becomes a search target. (Files that meet the conditions are subject to automatic merging).

  A display filter is applied under the conditions of the analysis tab, and the result is displayed. When the automatic activation check box in the Excel analysis setting field 1612 is turned on, Excel or Ethereal is automatically activated. In the case of Excel automatic activation, the csv output result can be confirmed. Since there is an inquiry about whether to enable the macro after starting Excel, enable it. After that, by browsing the csv file to be read, a list of analysis data is displayed (see FIG. 18). In the case of the automatic startup of Ethereal, the result of applying the display filter under the conditions of the analysis tab can be confirmed on the Ethereal.

  Next, an example of using the message trace tool will be described. As shown in FIG. 19A, on the message trace tool, a file output in the message trace format (for example, xxx_TraceTool.bin) and a destination for saving the definition document are designated. A message definition document must be created in advance.

  And as shown in FIG.19 (b), the message to display is selected in the following way. First, a definition re-read button 1901 is pressed to read a definition document, and a message No. is selected in a column 1902 to display a list of messages in a column 1903. When the message to be displayed in the field 1903 is selected, the message content is displayed as shown in FIG.

((4) Serial transmission diagnostic tool)
When a command button (not shown) is operated on the display device 11, a serial transmission diagnosis operation screen 1107 is displayed on the display device 11, as shown in FIG. In the serial transmission diagnosis operation screen 1107, reference numeral 1108 denotes a selection button for selecting whether to execute “infinite”, “schedule”, or “manual (once)”. Reference numeral 1109 denotes a diagnosis stop button for instructing to stop the diagnosis.

  FIG. 20 shows the flow of the serial transmission diagnosis process. First, data on the TCP / IP network NW (hereinafter referred to as TCP / IP data) is acquired (step S2001). Next, data (hereinafter referred to as serial transmission data) transmitted and received by the communication target device 400 is acquired (step S2002). Then, the data acquired in steps S2001 and S2002 are imported into the serial transmission diagnosis result sheet 13i shown in FIG. 9, and rearranged using the time as a key (step S2003).

  Next, a time difference ΔTd between the TCP / IP data and the serial transmission data is determined (step S2004). The time difference ΔTd is for correcting the time difference between the TCP / IP data and the serial transmission data due to the communication speed or the like, and this time difference determination process will be described later with reference to FIG.

  Next, the time data of the serial transmission data in the serial transmission diagnosis result sheet 13i is subtracted by ΔTd and rearranged again (step S2005).

  Next, before and after the time data of the serial transmission data in the serial transmission diagnosis result sheet 13i, specifically, within the scan time set in the common definition sheet 13a shown in FIG. The TCP / IP data is searched, and the row position in the sheet is switched so that the time order is correct (step S2006). In FIG. The items with □ (reception) and ■ (transmission) in the item are serial transmission data, and the data before and after that is TCP / IP data.

  In S2006, when it is diagnosed that there is no TCP / IP data corresponding to the serial transmission data, it is determined that the TCP / IP data is lost, an error notification is executed, and the predetermined location of the network configuration diagram sheet 13c is changed in color. It is displayed (step S2007). Also, a serial transmission diagnosis log sheet 13j is created.

  FIG. 21A shows the flow of the time difference determination process in step S2004. First, from-to (transmission, reception) and timeout of data set in the common definition sheet 13a are acquired (step S2101). In this example, the from data is set to ENQ, and the to data is set to ACK.

  Next, for both TCP / IP data and serial transmission data, the from data (ENQ) and to data (ACK) are searched from the head (step S2102). If there is no data in step S2102, the process proceeds to step S2105, and after-to (transmission, reception) of the data in the next row is acquired, then the process returns to step S2102.

  If there is data in step S2102, the process proceeds to step S2104, ΔTt and ΔTs are calculated, and it is determined whether both ΔTt and ΔTs are within the timeout range. Here, as shown in FIG. 21B, ΔTt is a time difference in data transmission / reception on the TCP / IP network NW side, and ΔTs is a time difference in data transmission / reception on the communication target device 400 side.

If ΔTt and ΔTs are not within the time-out range in step S2104, the process proceeds to step S2105, and after-to (transmission, reception) of the data in the next row is acquired, then the process returns to step S2102. If ΔTt and ΔTs are both within the timeout range in step S2104, the process proceeds to step S2106. In step S2106, a time difference ΔTd between the TCP / IP data and the serial transmission data is calculated by the following equation.
ΔTd = (ΔTt + ΔTs) / 2

  When the “manual (once)” button of the selection buttons 1108 on the serial transmission diagnosis operation screen 1107 is pressed, the processing of FIG. 20 is executed. When the “infinity” button is pressed among the selection buttons 1108, the processing in FIG. 20 is repeated until the diagnosis stop button 1109 is pressed. When the “schedule” button among the selection buttons 1108 is pressed, the processing in FIG. 20 is repeated according to the schedule set in the execution schedule sheet 13b until the diagnosis stop button 1109 is pressed.

  With the serial transmission diagnostic tool described above, data on the TCP / IP network NW and data transmitted and received by the communication target device 400 are always collected. For example, when a trouble occurs, the TCP / IP network NW in the designated time zone is collected. The above data and the data transmitted and received by the communication target device 400 can be merged in time series and diagnosed. Thereby, the cause investigation at the time of failure occurrence and the efficiency of the countermeasure implementation work can be improved.

  An object of the present invention is to supply a program of software that realizes the functions of the above-described embodiments to a system or apparatus, and a computer code (or CPU or MPU) of the system or apparatus stored in a storage medium. Needless to say, this can also be achieved by reading and executing.

  In this case, the program itself read from the storage medium realizes the functions of the above-described embodiments, and the program itself and the storage medium storing the program constitute the present invention. As a storage medium for supplying the program, for example, a flexible disk, a hard disk, an optical disk, a magneto-optical disk, a CD-ROM, a CD-R, a magnetic tape, a nonvolatile memory card, a ROM, or the like can be used.

It is a figure which shows the structural example of the process control system containing the diagnostic system to which this invention is applied. It is a figure which shows the function structure of a diagnostic apparatus. It is a figure for demonstrating a common definition sheet | seat. It is a figure for demonstrating an execution schedule sheet | seat. It is a figure for demonstrating a network block diagram sheet. It is a figure for demonstrating a network definition sheet. It is a figure for demonstrating a ping result sheet | seat. It is a figure for demonstrating SW list sheet. It is a figure for demonstrating a serial transmission diagnostic result sheet. It is a figure for demonstrating a serial transmission diagnostic log sheet. It is a figure which shows an operation screen. It is a flowchart which shows the flow of a ping issuing process. It is a flowchart which shows the process at the time of pushing down the "all node diagnosis (once)" button. It is a flowchart which shows the process at the time of pressing of a search start button. It is a flowchart which shows the process at the time of pressing of a ping button. It is a figure which shows a capture setting screen. It is a figure which shows a capture setting screen. It is a figure which shows the list display screen of analysis data. It is a figure which shows the screen at the time of message trace tool use. It is a flowchart which shows the flow of a serial transmission diagnostic process. It is a flowchart which shows the flow of a time difference determination process.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Diagnosis apparatus 2 Switching hub 100 Control server 200 Switching hub 300 Network apparatus 400 Communication object apparatus 500 Protocol converter 600 Branch cable 700 Serial transmission capture apparatus 800 Capture data storage part 11 Display apparatus 12 Input apparatus 13 Worksheet storage part 14 Ping issue Section 15 Diagnosis section 16 Display control section 17 CRC error monitoring section 18 Log output section 19 Capture section 20 Serial transmission data acquisition section

Claims (6)

A network that monitors and diagnoses a network system in which a network configured by connecting a plurality of devices and a communication target device that performs data communication using a communication protocol different from the communication protocol of the network is connected via a protocol converter A system diagnostic system,
First collecting means for collecting data on the network;
Second collection means for collecting data transmitted and received by the communication target device;
The data corresponding to the data transmitted and received by the communication target device collected by the second collection means among the data on the network collected by the first collection means is searched based on time, and spreadsheet software A diagnostic system for a network system, comprising: a transmission diagnostic means for outputting to a sheet created in (1).   The transmission diagnosis unit is diagnosed as having no data on the network collected by the first collection unit corresponding to data transmitted and received by the communication target device collected by the second collection unit. The network system diagnosis system according to claim 1, wherein an error notification is issued in the case.   When the diagnosis unit diagnoses that the data on the network collected by the first collection unit does not correspond to the data transmitted and received by the communication target device collected by the second collection unit The network system diagnosis system according to claim 1 or 2, wherein the network system configuration created by spreadsheet software is displayed on a display device by reflecting the configuration on the network configuration diagram.   The network system diagnosis system according to any one of claims 1 to 3, wherein the transmission diagnosis schedule can be set by an execution schedule sheet created by spreadsheet software. A network that monitors and diagnoses a network system in which a network configured by connecting a plurality of devices and a communication target device that performs data communication using a communication protocol different from the communication protocol of the network is connected via a protocol converter A system diagnostic method comprising:
Collecting data on the network;
A procedure for collecting data transmitted and received by the communication target device;
A step of searching for the data corresponding to the data transmitted and received by the communication target device among the collected data on the network on the basis of time, and outputting to a sheet created by spreadsheet software A network system diagnosis method characterized by the above. A process for monitoring and diagnosing a network system in which a network configured by connecting a plurality of devices and a communication target device that performs data communication using a communication protocol different from the communication protocol of the network is connected via a protocol converter A program for causing a computer to execute
Processing to collect data on the network;
A process of collecting data transmitted and received by the communication target device;
A process of searching the data corresponding to the data transmitted / received by the communication target device among the collected data on the network on the basis of time and outputting the result to a sheet created by spreadsheet software on a computer A program to be executed.

Images