JP2002082712A - Remote inspection system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a remote inspection system which speedily and accurately inspect a controlled device at a remote place. SOLUTION: A diagnosis requester presses a communication button on a touch panel 13 if a pressure welder becomes abnormal to send 'the user name, machine name, and machine number' of the pressure welder recorded in a PLC 12 and the ladder chart of the PLC 12 to a business office terminal 21. A diagnosing person diagnoses the fault on the business office terminal 21 while browsing the ladder chart, etc., of the PLC and sends the diagnosis result from the business office terminal 21 to the PLC 12. When the diagnosing person is absent, the business office terminal 21 accesses a database server 31 to obtain past fault causes and diagnosis results stored there and send them to the PLC 12. The diagnosis requester repairs the pressure welder while browsing the diagnosis results, etc., that the PLC 12 receives.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a remote inspection system for inspecting a device to be controlled at a remote location more quickly and accurately.

[0002]

2. Description of the Related Art Japanese Patent Laid-Open No.
08, the remote maintenance device disclosed in FIG.
9 will be described.

[0003] The device on the user side includes a plurality of devices 108 provided with a programmable logic controller (PLC 12) 111, a modular jack 110 provided in each device 108 and connected to a telephone line terminal 109, a modem 113, It comprises a portable maintenance unit 112 in which a diagnostic link unit 114 is stored.

[0004] The device on the maker side includes a personal computer 102 storing software for remote maintenance, and a modem 103 connected via a telephone line terminal 109 and a telephone line network 104 on the user side.

[0005] When a failure occurs in the device 108, the user connects the portable maintenance unit 112 to the modular jack 110 and the PLC 111. The diagnostician of the manufacturer operates the personal computer 102 to obtain the ladder state and the error log of the PLC 111 via the telephone network 104, and performs a failure diagnosis based on the data.

Therefore, the diagnostician of the manufacturer can diagnose the failure of the device 108 on the user side without going to the user side. In addition, the user does not need to install the diagnostic link unit 114, the modem 113, and the like for each of the devices 108 on the user side, and can reduce costs and the like.

[0007]

However, the above-described remote maintenance device has the following problems.

First, a diagnosing person of a manufacturer cannot quickly obtain identification information (customer name, model name, machine number, etc.) of a device on a user side, and a past failure of the device. Since data and diagnostic data cannot be known, quick and accurate failure diagnosis cannot be performed.

Second, a diagnostician cannot give advice to a user when an engineer performing a failure diagnosis is absent or the like.

[0010] Third, when parts are needed for repair work, the diagnostician cannot quickly provide the parts.

Accordingly, the present invention provides a remote inspection system which aims to solve such a problem and speed up and accurately perform a failure diagnosis.

[0012]

[Means for Solving the Problems and Effects of the Invention] (1)
A remote inspection system according to the present invention includes a control device that controls a device to be controlled, and a remote inspection device connected to the control device via a transmission unit. The control device includes control information and the control object. The apparatus is characterized in that the identification information of the device is transmitted to the remote inspection device via transmission means, and the remote inspection device transmits the inspection result to the control device via transmission means.

Therefore, the inspection requester can request the inspection quickly by transmitting the control information and the identification information of the control target device to the remote inspection device using the control device. On the other hand, the inspector can quickly perform the inspection based on the control information received by the remote inspection device and the identification information of the control target device, and transmit the inspection result to the control device.

(4) The inspection requesting device of the present invention provides a control device for controlling a control target device to a remote inspection device connected to the control device via a transmission means. It is characterized by transmitting device identification information.

Therefore, even if the control device does not have a function of transmitting control information and the like to the remote inspection device, the inspection requester can transmit the control information to the remote inspection device by using the inspection request device. can do.

(5) In the remote inspection system according to the present invention, the remote inspection device displays control information received from the control device and identification information of the control target device, and the control device includes the remote inspection device. Is characterized by displaying the inspection results received from the company.

Therefore, the inspector can browse the displayed control information and the identification information of the control target device, specify the control target device, and perform the inspection. On the other hand, the inspection requester can perform repair while viewing the displayed inspection result.

(6) In the remote inspection system according to the present invention, the control device may transmit the control information and the identification information of the control target device to the remote inspection device before transmitting the control information or the control device. The present invention is characterized in that a test requester is instructed to execute a diagnosis.

Therefore, the test requester can perform a self-diagnosis before requesting the test.

(7) The remote inspection system according to the present invention is characterized in that the control device transmits self-diagnosis information to the remote inspection device together with control information and identification information of the control target device.

Therefore, the examiner can also obtain information on self-diagnosis, and can use this information to perform more accurate examinations.

(8) In the remote inspection system according to the present invention, a failure history database is provided so as to be accessible from the remote inspection device, and the remote inspection device includes at least control information received from the control device. ,
The apparatus is characterized in that failure history information is extracted from the failure history database based on identification information of the control target device or information on self-diagnosis.

Therefore, when the inspector is absent or the like, the failure history information can be automatically transmitted to the control device as the inspection result. On the other hand, the inspection client can use the failure history information to perform more accurate repair.

(9) In the remote inspection system according to the present invention, an inspection history database is provided so as to be accessible from the remote inspection device, and the remote inspection device includes at least control information received from the control device. ,
The apparatus is characterized in that inspection history information is extracted from the inspection history database based on identification information of the control target device or information on self-diagnosis.

Therefore, when the inspector is absent or the like, the inspection history information can be automatically transmitted to the control device as the inspection result. On the other hand, the inspection client can use the inspection history information to perform more accurate repair.

(10) In the remote inspection system according to the present invention, an inventory information database is provided so as to be accessible from the remote inspection device, and the remote inspection device includes at least control information received from the control device. ,
The system is characterized in that inventory information is extracted from the inventory information database based on the identification information of the control target device or information on self-diagnosis.

Therefore, the inspector can provide more accurate advice using the stock information of the parts. On the other hand, the inspection client can quickly acquire the parts required for the repair work.

(11) In the remote inspection system according to the present invention, the control device detects an abnormality based on the control information and transmits control information and identification information of the control target device to the remote inspection device. It is characterized by:

Therefore, when the inspection requester is absent or the like, an abnormality can be automatically detected and an inspection can be requested.

(12) In the remote inspection system according to the present invention, the control device stores connection information of the remote inspection device, and based on the connection information, controls the control information and the identification information of the control target device. , Transmitted to the remote inspection device via transmission means.

Therefore, the inspection client can transmit control information and the like to the remote inspection device without inputting connection information to the control device.

The controlled device is controlled by the control device, and corresponds to the press machine of the press machine system 11 in the following embodiment.

The control device controls the device to be controlled. In the embodiment described below, the programmable logic controller (P
LC12) and the touch panel 13.

The remote inspection device is a device connected to the control device via a transmission means, and corresponds to the office terminal 21 in the following embodiment.

The inspection request device is for transmitting control information and the like from the control device to the remote inspection device. In the following embodiment, a notebook computer storing the diagnosis request software 121 corresponds to the inspection request device.

The failure history database stores failure history information. In the following embodiment, the failure / diagnosis history database 3 of the database server 31 will be described.
11 corresponds to this.

The inspection history database stores the inspection history information. In the following embodiment, the failure / diagnosis history database 3 of the database server 31 is used.
11 corresponds to this.

The stock information database is for storing stock information, and corresponds to the stock parts database 312 of the database server 31 in the following embodiment.

The control information is information for controlling the device to be controlled. In the following embodiment, the PLC 1
2 corresponds to the ladder chart.

The identification information of the device to be controlled is information for identifying the device to be controlled, and corresponds to the "user name, model name, and machine number" of the crimping machine in the following embodiment.

The inspection result is a concept including failure history information, inspection history information, stock information, and the like in addition to information on the result of the inspection performed by the inspector. In the following embodiment, the diagnosis result, the failure history data , Diagnosis history data, and the like.

The failure history information is information stored in a failure history database, and in the following embodiment,
This corresponds to failure history data.

The inspection history information is information stored in the inspection history database, and in the following embodiment,
This corresponds to the diagnosis history data.

The connection information of the remote inspection device is information for the control device to make a communication connection with the remote inspection device, and corresponds to a telephone number of a business office requesting a repair work in the following embodiment.

[0045]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS A description will be given below, by way of example, of a case where maintenance is performed for a failure of an automatic pressure welding machine used for manufacturing a wire (harness) with a connector.

1. Overall Configuration FIG. 1 shows the overall configuration of a remote inspection system according to an embodiment of the present invention.

The crimping machine system 11 on the diagnosis requester side comprises a crimping machine, a programmable logic controller (PLC 12) for controlling the crimping machine, and a touch panel 1
3 is provided. Further, there is provided an abnormality occurrence lamp 14 which is turned on when an abnormality occurs in the pressure welding machine. This PLC12
, "User name, model name, machine number" and "telephone number" of the business office requesting the failure diagnosis are recorded in advance.

The office terminals 21 and 22 on the manufacturer side are communicably connected to the PLC 12 on the diagnosis requester side via a telephone line. The database server 31 is connected to a plurality of office terminals 21 and 22 via dedicated lines. This stores data such as past causes of failure of each press welding machine.

The diagnosis requester using this system connects the PLC 12 to the telephone line terminal when the abnormality occurrence lamp 14 of the insulation displacement machine is turned on. The PLC 12 transmits the “user name, model name, and machine number” of the crimping machine and the ladder chart of the PLC 12 to the business office terminal 21.

The diagnostician makes a failure diagnosis while viewing the ladder chart and the like of the PLC 12 on the display of the business office terminal 21, and transmits the diagnosis result from the business office terminal 21 to the PLC 12. When the diagnostician is absent or the like, the sales office terminal 21 accesses the database server 31 to obtain the past failure causes and diagnostic results stored therein, and transmits them to the PLC 12.

The diagnosis requester repairs the crimping machine while viewing the diagnosis result and the like received by the PLC 12 on the touch panel 13.

With such a use, the diagnostician can easily specify the type of the crimping machine to be diagnosed, and can quickly diagnose the failure. In addition, the diagnosis requester
Requests for diagnosis can be made promptly.

2 Hardware Configuration of Business Office Terminal 21 FIG. 2 shows a hardware configuration example of the business office terminal 21 shown in FIG. To the CPU 21a, via a bus line,
A memory 21b, a display 21c, an input device 21d,
Hard disk 21e, CD-ROM drive 21f,
The modem 21g is connected.

The hard disk 21e has registered therein diagnostic support software 211, an operating system 212 (such as Microsoft Windows), and the like.
The diagnostic support software 211 is a CD-ROM drive 2
1f, which is installed from the CD-ROM 21h.

The diagnostic support software 211 is a PLC 12
The ladder chart and the like of the PLC 12 received from the PC 21 are displayed on the display 21c, and the "user name, model name, machine number" of the press-welding machine is transmitted to the database server 31.

In this embodiment, the diagnostic support software 2
11, in cooperation with operating system 212,
Perform the above functions.

3 Database server 31 FIG.
3 shows a hardware configuration example of the database server 31 shown in FIG. A memory 31b, a display 31c, an input device 31d, a hard disk 31e, a CD-ROM drive 31f, and an interface 31g are connected to the CPU 31a via a bus line.

The hard disk 31e has a failure / diagnosis history database 311, a stock parts database 312,
Parts list table 313, advice selection software 31
4. Inventory information detection software 315, parts information detection software 3
16 and an operating system 317 are registered. These software are stored in the CD-ROM drive 31
The software is installed from the CD-ROM 31h via f.

The failure / diagnosis history database 311 includes:
Failure history data and diagnosis history data are registered in association with “user name, model name, machine number” (see FIG. 10). Note that the failure history data is data of the cause of a failure that has occurred in the past. The diagnosis history data is data of a diagnosis result performed in the past.

The stock information of the part is registered in the stock part database 312 in association with the part name and the model number (see FIG. 14).

In the parts list table, a list of parts of the crimping machine is registered in association with the "model name" (see FIG. 15).

The advice selection software 314 extracts failure history data and diagnosis history data from the failure / diagnosis history database 311 using “user name, model name, machine number” as a key.

The stock information detection software 315 uses “part name,
The stock information of the part is detected from the stock part database 312 using the "model number" as a key.

The component information detection software 316 is provided with “model name”
Is used as a key to detect a parts table of the model from the parts list table 313.

In this embodiment, the advice selection software 314, the stock information detection software 315, and the component information detection software 316 execute the above functions in cooperation with the operating system 317.

4 Configuration of IDC System FIG. 4 shows the configuration of the ID system 11 shown in FIG.
The pressure welding machine system 11 includes a pressure welding machine, a PLC 12, a touch panel 13, and an abnormality occurrence lamp 14.

The PLC 12 includes diagnosis request software 12
1. A ladder chart (control program of the crimping machine), “user name, model name, machine number” of the crimping machine are registered. The PLC 12 has a modem interface unit.

The diagnosis requesting software includes the “user name, model name, machine number” of the crimping machine recorded in the PLC 12 and the PLC 12
Is transmitted to the sales office terminal 21.

The modem interface unit is a PL
This is for connecting C12 to a telephone line terminal.

4 Flowchart The processing of the diagnosis request software 121 of the PLC 12 when making a diagnosis request and the sales office terminal 21 when making a diagnosis are described below.
Diagnostic support software 211, database server 31
Advice selection software 314, inventory information detection software 3
15. The processing of the component information detection software 316 will be described using 4.1 to 4.6 as an example.

4.1 Diagnosis Based on the Ladder Chart of the PLC 12 FIG. 5 shows the diagnosis request software 121 of the PLC 12 and the diagnosis support software 211 of the business office terminal 21 when the diagnosis is performed based on the ladder chart of the PLC 12. Indicates processing.

First, when the abnormality occurrence lamp 14 of the insulation displacement machine is turned on, the diagnosis requester presses the communication button on the touch panel 13 to request a diagnosis (ST11). PLC12
The diagnosis request software 121 transmits the “user name, model name, machine number” of the press-welding machine recorded in the PLC 12 and the ladder chart of the PLC 12 to the business office terminal 21 via the telephone line (ST12). .

The diagnostic support software 21 of the business office terminal 21
Upon receiving the ladder chart or the like of the PLC 12, the 1 displays a request reception page as shown in FIG. 6 on the display 21c (ST13).

The diagnostician browses the “user name (customer name), model name, machine number” displayed on the request receiving page, and
A monitoring button is input (ST14). The diagnostic support software 211 displays the ladder chart of the PLC 12
It is displayed on the display 21c (ST15) (see FIG. 7).

The diagnostician browses the ladder chart, performs a failure diagnosis, inputs the diagnosis result, the recovery method to the office terminal 21 (ST16), and inputs a completion button (ST17) (FIG. 8). The diagnosis support software 211 transmits the diagnosis result and the recovery method to the PLC 12 via the telephone line (ST18).

When the diagnosis request software 121 of the PLC 12 receives the diagnosis result and the recovery processing method, the
Is displayed (ST19). The diagnosis requester repairs the crimping machine while viewing the diagnosis result and the restoration treatment method.

With such a use, the diagnostician can easily specify the type of the pressure welding machine and the like, and can quickly provide a diagnosis result.

4.2 When Providing Failure History Data and Diagnosis History Data FIG. 9 shows the diagnosis request software 121 of the PLC 12, the diagnosis support software 211 of the business office terminal 21, and the database when providing the failure history data and the diagnosis history data. The processing of the advice selection software 314 of the server 31 is shown.

Similarly to 4.1, upon receiving the ladder chart or the like of the PLC 12, the diagnostic support software 211 of the office terminal 21 displays a request reception page on the display 21c (ST21 to ST23). The diagnostician browses the “user name, model name, machine number” displayed on the request reception page and inputs a history search button (ST24). The diagnostic support software 211 uses the “user name, model name,
The machine number is transferred to the database server 31 via a dedicated line.
(ST25).

When the "user name, model name, model number" is received, the advice selection software 314 of the database server 31 uses the data as a key to generate a fault
The failure history data and the diagnosis history data are detected from the diagnosis history database 311 (ST26). Then, the failure history data and the diagnosis history data are transferred via a dedicated line,
The information is transmitted to the office terminal 21 (ST27).

The diagnostician confirms the failure history data and the like on the history data reception page of FIG. 11 and transmits the data to the PLC 12 by inputting the transmission button (ST28, 29).

Upon receiving the failure history data and the like, the diagnosis request software 121 of the PLC 12 displays the failure history data and the diagnosis history data on the touch panel 13 (ST30).
The diagnosis requester repairs the insulation displacement machine while viewing the failure history data and the diagnosis history data.

By using this method, the diagnosis requester can obtain the cause of the past failure and the diagnosis result.

4.3 When Diagnosis is Performed Using Failure History Data and Diagnosis History Data FIG. 12 shows a case where a more accurate diagnosis result is provided using the failure history data and diagnosis history data.
3 shows the processing of the diagnosis request software 121, the diagnosis support software 211 of the office terminal 21, and the advice selection software 314 of the database server 31.

As in the above section 4.2, the database server 3
The first advice selection software 314 uses the “user name, model name, machine number” received from the sales office terminal 21 as a key.
Failure history data and diagnosis history data are detected from the failure / diagnosis history database 311 (ST41 to ST46). Then, these data are transmitted to the office terminal 21 (ST47).

The diagnostic support software 21 of the business office terminal 21
1 receives the failure history data and the like, displays the failure history data and the diagnosis history data on the display 2 of the sales office terminal 21.
1c (ST48).

The diagnostician refers to these data and
Enter the monitoring button on the request receiving page (ST4
9), also browse the ladder chart of PLC 12 (ST5)
0). Then, a failure diagnosis is performed, and the diagnosis result is
(ST51, 52).

With such use, the diagnostician can refer to the failure history data and the diagnosis history data, so that a more accurate diagnosis result can be provided.

4.4 Case of Providing Information on Inventory Parts FIGS. 13A to 13C show diagnosis request software 121 of the PLC 12 for promptly providing parts necessary for repair work.
The processing of the diagnostic support software 211 of the office terminal 21, the advice selection software 314, the stock information detection software 315, and the parts information detection software 316 of the database server 31 will be described.

4.4.1 Detection of Stock Information As in the case of 4.1, the diagnostician browses the ladder chart of the PLC 12 (ST61 to ST65) and determines whether or not parts are necessary for repair work. When the diagnostician determines that a part is necessary, the user inputs a history search button on the request reception page to acquire failure history data and diagnosis history data from the database server 31 (ST66 to ST66).
0).

When the diagnostician can know the model numbers of the parts necessary for the repair work from the failure history data, etc.
In the history data reception page shown in FIG. 1, the part name and model number are input to the office terminal 21 (ST71), and an inventory search button is input (ST72). The diagnosis support software 211 of the office terminal 21 transmits the part name and the model number to the database server 31 (ST73).

The stock information detection software 315 of the database server 31 uses FIG.
Is detected from the stock parts database 312 (ST74).

[0093] Further, the diagnostician can determine from the failure history data and the like.
If the model number of the component required for the repair work cannot be known, the user inputs a component search button on the history data reception page shown in FIG. 11 (ST91). The diagnosis support software 211 of the office terminal 21 transmits the "model name" to the database server 31 (ST92).

The part information detection software 316 of the database server 31 detects the part of the model from the parts list table 313 shown in FIG. 15 using the "model name" as a key (ST93), and uses it as a parts table to make the sales office. It transmits to terminal 21 (ST94).

[0095] Diagnosis support software 21 of business office terminal 21
1 receives the bill of materials and displays it on display 2
1c (ST95). The diagnostician browses the parts list and specifies the model number of the parts required for the repair work. Then, on the history data reception page shown in FIG. 11, the part name and the model number are input to the office terminal 21 (ST71), and the stock search button is input (ST72). Office terminal 21
Of the diagnostic support software 211 of the database server 3
Then, the part name and the model number are transmitted to ST1 (ST73).

The stock information detection software 315 of the database server 31 detects stock information of the part from the stock part database 312 using the part name and the model number as keys (ST74).

4.4.2 Diagnosis Processing The following processing is performed based on the presence or absence of stock parts.

If there is a stock part, a screen for instructing the client to send the part is displayed on the display 31c of the database server 31 (ST75, ST7).
6). Then, the fact that there is a stock part is transmitted to the office terminal 21 (ST77).

In response to this, the diagnostician browses the ladder chart of the PLC 12, makes a failure diagnosis, and transmits a diagnosis result to the PLC 12 (ST80, 81).

If there is no stock part, the database server 3 displays a screen for instructing the part company to order the part.
1 is displayed on the display 31c (ST75, ST7).
8). Then, the fact that there is no stock part is transmitted to the office terminal 21 (ST79).

In response to this, the diagnostician informs the sales office terminal 21 of the fact that there is no stock part and takes a countermeasure taking that into account.
The data is transmitted to the LC 12 (ST80, 81).

If the diagnostician determines in ST65 that the part is not necessary, there is no need to detect the stock information, so that the failure diagnosis is performed by browsing the ladder chart of the PLC 12 in the same manner as in 4.1.

By using such a method, the diagnosis requester can quickly acquire the stock parts, if any, when they exist. On the other hand, the diagnostician can provide advice based on the presence or absence of the stock parts.

4.5 Automatically Providing Diagnosis History Data, etc. FIG. 16 shows the diagnosis request software 121 of the PLC 12 for automatically providing diagnosis history data, etc., when the diagnostician is absent. Diagnosis support software 21 for office terminal 21
1. Advice selection software 3 for database server 31
14 shows the process.

Diagnosis support software 21 for business office terminal 21
When receiving the "user name, model name, machine number" of the press-welding machine and the ladder chart of the PLC 12 from the PLC 12, an automatic diagnosis instruction is received and an abnormal portion (for example, "cutting blade") in the ladder chart is determined. Detect (ST101 to ST101
04). This automatic diagnosis command is issued to the office terminal 21 when the diagnostician is absent or the like. And
`` User name, model name, machine number '' and abnormal location `` cutting blade ''
The data is transmitted to the database server 31 (ST105).

The advice selection software 314 of the database server 31 retrieves failure history data from the failure / diagnosis history database 311 shown in FIG. 10 by using “user name, model name, machine number” and abnormal location “cutting blade” as keys. "Sensor 0
80 failure "and the diagnostic history data" Replace the sensor 080 "are detected (ST106). And
These data are transmitted to the office terminal 21 (ST1).
07).

Diagnosis support software 21 for business office terminal 21
1 receives the failure history data and the diagnosis history data,
These data are transmitted to the PLC 12 (ST10
8, 109).

With such a use, advice can be automatically provided even when the diagnostician is absent.

4.6 Case of Providing Inventory Parts Quickly FIG.
2 shows processing of the diagnosis request software 121, the diagnosis support software 211 of the office terminal 21, the advice selection software 314 of the database server 31, the stock information detection software 315, and the parts information detection software 316.

Diagnosis support software 21 for business office terminal 21
When the PLC 1 receives the "user name, model name, and machine number" of the press-welding machine and the ladder chart of the PLC 12 from the PLC 12, it receives an automatic diagnosis command and detects an abnormal portion in the ladder chart (ST111 to ST114). And
The “user name, model name, machine number” and the abnormal part are transmitted to the database server 31 (ST115).

The advice selection software 314 of the database server 31 uses the “model name, machine number” and the abnormal part as keys, and displays the failure / diagnosis history database 311 shown in FIG.
From the failure history data and the diagnosis history data (S
T116), a part name and a model number necessary for the repair work are specified (ST117).

The inventory information detection software 315 of the database server 31 detects inventory information from the inventory component database 312 using the component name and model number as keys (ST11).
8).

If there are stock parts, a screen for instructing the diagnosis client to send the parts is displayed on the display 31c of the database server 31 (ST119).
Then, the fact that there is a stock part, failure history data, and diagnosis history data are transmitted to the office terminal 21 (ST120).

In response to this, the diagnosis support software 211 of the office terminal 21 transmits the data to the PLC 12 (ST121, ST122).

[0115] By using this method, it is possible to quickly provide parts necessary for repair work even when the diagnostician is absent. 5 In this embodiment, when the diagnosis requester confirms the lighting of the abnormality occurrence lamp 14, the
Is transmitted to the business office terminal 21.
However, the present invention is not limited to this.
2 may be provided with self-diagnosis software, and the software may instruct the diagnosis requester to make a self-diagnosis (for example, “Please confirm the position of the sensor 080”). In this case, P
The diagnosis request software 121 of the LC 12 transmits the result of the self-diagnosis to the office terminal 21 together with the ladder chart of the PLC 12 and the like.

Further, the diagnosis support software 211 of the business office terminal 21 transmits a self-diagnosis message (for example, “sensor 0
Check the position of 80. )) As a key, an abnormal portion (for example, “cutting blade”) on the ladder chart may be searched. In this case, upon receiving the input of the monitoring button by the diagnostician, the abnormal portion "cutting blade" is immediately displayed on the display 21c.

Further, the diagnosis support software 211 of the office terminal 21 may transmit a self-diagnosis message to the database server 31. In this case, the advice selection software 314 of the database server 31 may detect failure history data and the like from the failure / diagnosis history database 311 using the self-diagnosis message as a key. 6 In this embodiment, the diagnosis requester confirms the lighting of the abnormality occurrence lamp 14 and inputs a communication button on the touch panel 13 to transmit a ladder chart or the like of the PLC 12 to the office terminal 21. However, the present invention is not limited to this. The PLC 12 is provided with abnormality detection software, and the software automatically detects the PLC 1
The ladder chart 2 and the like may be transmitted to the business office terminal 21.

In this embodiment, the advice selection software 314 of the database server 31 uses the “user name, model name, machine number” as a key to retrieve failure history data and diagnosis history data from the failure / diagnosis history database 311. Has been detected. However, the present invention is not limited to this, and failure history data or the like may be detected using only the “model name” as a key. In this case, the amount of failure history data,
The diagnosis history data amount increases, and the diagnosis requester can easily perform repair work.

In this embodiment, the database server 31 transmits the presence or absence of stock parts to the sales office terminal 21 based on stock information in the stock parts database 312 (see ST77 and 79 in FIG. 13B). . However, the present invention is not limited to this, and detailed stock information (for example, the number of stock parts at each sales office or branch) may be transmitted to the sales office terminal 21. In such a case, by transmitting the detailed inventory information to the PLC 12 as well, the office terminal 21 can provide more useful information to the diagnosis requester.

In this embodiment, the office terminal 21 and the database server 31 are provided separately.
However, the present invention is not limited to this, and the failure / diagnosis history database 311 and the stock parts database 312 may be stored in the office terminal 21.

In this embodiment, the failure history data and the like are transmitted from the database server 31 to the sales office terminal 2.
1 to the PLC 12. However, the present invention is not limited to this, and the data may be directly transmitted from the database server 31 to the PLC 12.

In this embodiment, when the diagnosis requester inputs a communication button on the touch panel 13, the ladder chart of the PLC 12 is displayed on the business office terminal 2.
Sending to 1. However, the present invention is not limited to this.
A ladder chart or the like of the LC 12 may be transmitted to the business office terminal 21. For example, the PLC 12 receives the input of the monitoring button on the request reception page by the diagnostician, and
Is transmitted to the sales office terminal 21.

Further, failure / diagnosis information registration software is stored in the sales office terminal 21, and the software stores diagnosis results and the like in the failure / diagnosis history database 311, failure history data,
It may be registered as diagnosis history data.

In this embodiment, the failure / diagnosis history database 311 records failure history data and diagnosis history data. However, the present invention is not limited to this, and either one may be used. In this case, the diagnosis requester is provided with one of the data.

Further, in this embodiment, the PLC 1
2 stores the diagnostic request software 121 and transmits a ladder chart or the like of the PLC to the business office terminal 21. However, the present invention is not limited to this.
A ladder chart or the like of the PLC may be transmitted to the office terminal 21 by connecting a notebook personal computer or the like storing the PLC 21 to the PLC 12.

Further, instead of the business office terminal 21, a server that receives a failure diagnosis on the web may be used.
In this case, the diagnosis requester can request a failure diagnosis by accessing the server from a terminal connected to the PLC.

In this embodiment, the case where the maintenance of the control system of the pressure welding machine is performed is described as an example. However, the present invention is not limited to this, and maintenance for other control systems may be performed. Further, the present invention is not limited to the case where maintenance is performed, but may be a case where a control program is changed or the like.

In this embodiment, when the diagnosis requester inputs a communication button on the touch panel 13, the PLC 12 operates the predetermined business office terminal 21.
Connect to However, the diagnosis requester may be able to arbitrarily determine the connection destination on the touch panel 13. This will be described with reference to FIG.

For example, when the diagnosis requester wants to request a diagnosis from the technical center in consideration of the failure history data and the like, the user selects the technical center on the touch panel 13 and displays the ladder chart of the PLC 12 on the terminal of the technical center. 51. In addition, sales office terminal 2
One diagnostician may be able to transmit and receive a PLC ladder chart between the business office terminal 21 and the technical center terminal 51 in order to request a diagnosis from the technical center in consideration of the failure history data and the like. .

[Brief description of the drawings]

FIG. 1 is a diagram illustrating an overall configuration of a remote inspection system according to an embodiment.

FIG. 2 is a diagram illustrating a hardware configuration of a business office terminal 21 in the embodiment.

FIG. 3 is a diagram illustrating a hardware configuration of a database server 31 according to the embodiment.

FIG. 4 is a diagram illustrating an entire configuration of a pressure welding machine system 11 according to the embodiment.

FIG. 5 is a diagram showing a diagnosis request software 121 of the PLC 12 and a diagnosis support software 2 of the business office terminal 21 for performing a diagnosis based on a ladder chart of the PLC 12 in the embodiment.
It is a figure which shows the process of No. 11.

FIG. 6 is a diagram showing a request reception page displayed on a display 21c of the business office terminal 21 in the embodiment.

FIG. 7 is a diagram showing a ladder chart of the PLC 12 displayed on the display 21c of the business office terminal 21 in the embodiment.

FIG. 8 is a diagram showing a screen when a diagnostician inputs a diagnostic result to the office terminal 21 in the embodiment.

FIG. 9 is a diagram showing diagnosis request software 1 of the PLC 12 for providing failure history data and diagnosis history data in the embodiment.
21 is a diagram showing processing of diagnostic support software 211 of the office terminal 21 and advice selection software 314 of the database server 31.

FIG. 10 is a diagram showing a failure / diagnosis history database 311 stored in the database server 31 in the embodiment.

FIG. 11 is a diagram showing a history data reception page displayed on a display 21c of the business office terminal 21 in the embodiment.

FIG. 12 is a diagram showing a diagnosis request software 121 of the PLC 12 and a sales office terminal 2 for providing more accurate diagnosis results by using the failure history data and the diagnosis history data in the embodiment.
1 diagnostic support software 211, database server 3
FIG. 11 is a diagram showing processing of one piece of advice selection software 314.

FIG. 13A is a diagram illustrating a diagnosis request software 121 of the PLC 12 and a diagnosis support software 2 of the business office terminal 21 when quickly providing parts required for repair work in the embodiment.
11 is a diagram illustrating processing of advice selection software 314, inventory information detection software 315, and component information detection software 316 of the database server 31.

FIG. 13B is a diagram showing a diagnosis requesting software 121 of the PLC 12 and a diagnosis support software 2 of the business office terminal 21 for quickly providing parts required for repair work in the embodiment.
11 is a diagram showing processing of advice selection software 314, inventory information detection software 315, and component information detection software 316 of the database server 31.

13C is a diagram illustrating a diagnosis request software 121 of the PLC 12 and a diagnosis support software 2 of the business office terminal 21 in a case where components required for the repair work are promptly provided in the embodiment.
11 is a diagram illustrating processing of advice selection software 314, inventory information detection software 315, and component information detection software 316 of the database server 31.

FIG. 14 is a diagram showing a stock parts database 312 stored in a database server 31 according to the embodiment.

FIG. 15 is a diagram showing a parts list table 313 stored in the database server 31 according to the embodiment.

FIG. 16 is a diagram illustrating a diagnosis request software 121 of the PLC 12 and a diagnosis support software 2 of the business office terminal 21 when automatically providing more accurate diagnosis history data and the like in the embodiment.
11 is a diagram showing processing of the advice selection software 314 of the database server 31. FIG.

FIG. 17 is a diagram illustrating a diagnosis request software 121 of the PLC 12, a diagnosis support software 211 of the office terminal 21, an advice selection software 314 of the database server 31, a stock information detection software 315, FIG. 9 is a diagram showing processing of information detection software 316.

FIG. 18 is a diagram illustrating an overall configuration of a remote inspection system according to the embodiment.

FIG. 19 is a diagram showing an entire configuration of a remote maintenance device according to a conventional technique.

[Explanation of symbols]

 12 PLC 21 Sales office terminal 311 Failure / diagnosis history database 312 Inventory parts database

Continued on front page F-term (reference) 5H223 AA06 AA15 CC03 DD07 DD09 EE06 5K048 AA04 BA21 CA08 DA02 DC04 DC07 EA11 EB02 EB03 EB08 EB12 FB04 FB08 FC01 GB01 GB05 GC01 HA01 HA02 HA05 HA07 HA13 HA22 5K101 NN11 NN03 NN03 NN03 NN03 RR11 SS07 TT06 UU16

Claims (14)

[Claims] 1. A remote inspection system comprising: a control device for controlling a control target device; and a remote inspection device connected to the control device via a transmission unit, wherein the control device includes control information and The remote inspection device transmits identification information of the control target device to the remote inspection device via transmission means, and the remote inspection device transmits an inspection result to the control device via transmission means. system. 2. A remote inspection device connected via a transmission unit to a control device for controlling a control target device, the control device receiving control information and identification information of the control target device from the control device, Is transmitted to the control device via a transmission unit. 3. A control device connected to a remote inspection device via transmission means for controlling a control target device, wherein the control information and the identification information of the control target device are transmitted to the remote inspection device via transmission means. A control device for transmitting to a control device. 4. A control device for controlling a control target device, comprising:
An inspection requesting device for transmitting control information and identification information of the control target device to a remote inspection device connected to the control device via a transmission unit. 5. The remote inspection system, remote inspection device or control device according to claim 1, wherein said remote inspection device displays control information received from said control device and identification information of said control target device. The control device displays an inspection result received from the remote inspection device. 6. The remote inspection system, the remote inspection device or the control device according to claim 1, wherein the control device transmits control information and identification information of the control target device to the remote inspection device. And instructing an inspection requester to execute a self-diagnosis of the control target device or the control device. 7. The remote inspection system, remote inspection device, or control device according to claim 6, wherein the control device transmits self-diagnosis information to the remote inspection device together with control information and identification information of the control target device. What is characterized by doing. 8. The remote inspection system, remote inspection device, or control device according to claim 1, wherein a failure history database is provided so as to be accessible from said remote inspection device. And extracting failure history information from the failure history database based on at least control information received from the control device, identification information of the control target device, or self-diagnosis information. 9. The remote inspection system, remote inspection device or control device according to claim 1, wherein an inspection history database is provided so as to be accessible from said remote inspection device. And extracting test history information from the test history database based on at least control information received from the control device, identification information of the control target device, or self-diagnosis information. 10. The remote inspection system, the remote inspection device or the control device according to claim 1, wherein an inventory information database is provided so as to be accessible from said remote inspection device. And extracting inventory information from the inventory information database based on at least control information received from the control device, identification information of the control target device, or self-diagnosis information. 11. The remote inspection system, the remote inspection device or the control device according to claim 1, wherein the control device detects an abnormality based on the control information, and controls the control information and the control target device. The identification information is transmitted to the remote inspection device. 12. The remote inspection system, the remote inspection device, or the control device according to claim 1, wherein the control device stores connection information of the remote inspection device, and based on the connection information, Control information and identification information of the control target device are transmitted to the remote inspection device via transmission means. 13. A remote inspection method implemented by using a control device for controlling a control target device and a remote inspection device connected to the control device via a transmission unit, wherein the control device includes: Control information and identification information of the control target device are transmitted to the remote inspection device via transmission means, and the remote inspection device transmits an inspection result to the control device via transmission means. Remote inspection method. 14. The remote inspection method according to claim 13, wherein in said remote inspection device, failure history information is based on at least control information received from said control device, identification information of said control target device, or self-diagnosis information. Alternatively, it is characterized by extracting inspection history information.