DIAGNOSTIC TOOL HAVING HUMAN-MACHINE INTERFACE, AND METHOD FOR DIAGNOSIS OF PROGRAMMABLE LOGIC CONTROLLER

Abstract

Examples of a diagnostic tool include a LAN port, a human-machine interface (HMI), and a CPU configured to transmit a command issued from the HMI by a user to a connection destination of the LAN port, wherein the diagnostic tool is configured to be incapable of wireless communication.

Claims

1. A diagnostic tool comprising: a LAN port; a human-machine interface (HMI); and a CPU configured to transmit a command issued from the HMI by a user to a connection destination of the LAN port, wherein the diagnostic tool is configured to be incapable of wireless communication.

2. The diagnostic tool according to claim 1, wherein the HMI is a touch panel.

3. The diagnostic tool according to claim 1, wherein the HMI comprises a display, a mouse, and a keyboard.

4. The diagnostic tool according to claim 1, further comprising an attaché case in which the LAN port, the HMI and the CPU are accommodated.

5. The diagnostic tool according to claim 1, further comprising a USB port configured to store data displayed at the HMI in an external memory.

6. The diagnostic tool according to claim 1, further comprising an IEC connector for power supply, and an AC-DC conversion circuit configured to support an input voltage from 85 to 265 V.

7. The diagnostic tool according to claim 1, wherein the diagnostic tool causes the HMI to display an internal state of a programmable logic controller (PLC) connected to the LAN port.

8. The diagnostic tool according to claim 1, wherein the diagnostic tool causes the HMI to display details of an alarm of a programmable logic controller (PLC).

9. The diagnostic tool according to claim 5, wherein data is given and received only via the LAN port and the USB port.

10. A method for diagnosis of a PLC, comprising: connecting a diagnostic tool including a human-machine interface (HMI) to a programmable logic controller (PLC); and causing the HMI to display an internal state of the PLC.

11. The method for diagnosis of the PLC according to claim 10, further comprising: causing the HMI to display a configuration screen including the PLC and equipment connected to the PLC; and displaying a state of the PLC or the equipment by selecting the PLC or the equipment displayed on the configuration screen.

12. The method for diagnosis of the PLC according to claim 11, wherein the equipment is a sensor, a switch, a motor or a lamp.

13. The method for diagnosis of the PLC according to claim 10, further comprising: causing the HMI to display an alarm list issued from the PLC; and causing the HMI to display details of an alarm by selecting the alarm displayed in the alarm list.

14. The method for diagnosis of the PLC according to claim 10, further comprising: displaying a forced operation screen for forcedly operating equipment connected to the PLC by depressing a button that exists at the HMI and is invisible to a user using a method determined in advance; and forcedly operating the equipment by operating the forced operation screen.

15. The method for diagnosis of the PLC according to claim 14, wherein the HMI is a touch panel, and a user forcedly operates the equipment by touching part of the forced operation screen.

16. The method for diagnosis of the PLC according to claim 10, wherein the PLC is connected to the HMI using a hot connect function via an Ethernet cable.

17. The method for diagnosis of the PLC according to claim 10, further comprising operating a logic program within the PLC from the HMI.

18. The method for diagnosis of the PLC according to claim 10, further comprising causing the HMI to display a state of an interlock of equipment connected to the PLC by operating the HMI.

19. The method for diagnosis of the PLC according to claim 18, further comprising causing the HMI to display whether or not the interlock normally functions.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0008] FIG. 1 is a perspective view of a diagnostic tool;

[0009] FIG. 2 is a perspective view of the attaché case in a closed state;

[0010] FIG. 3A is a plan view of inside of the attaché case;

[0011] FIG. 3B is a cross-sectional diagram of the attaché case;

[0012] FIG. 3C is a cross-sectional diagram of the attaché case;

[0013] FIG. 4 is a view illustrating a connection example of the diagnostic tool;

[0014] FIG. 5 illustrates one CPU unit, and NODEs connected as slaves;

[0015] FIG. 6 shows I/O of the equipment connected to the CPU unit;

[0016] FIG. 7 is a view illustrating an example of the forced operation screen;

[0017] FIG. 8 shows interlock display screen;

[0018] FIG. 9 is a view illustrating an example of an alarm list display screen;

[0019] FIG. 10 is a view illustrating an example of the alarm detailed screen;

[0020] FIG. 11 is a block diagram of the HMI in a case where the processing circuitry is dedicated hardware; and

[0021] FIG. 12 is a block diagram illustrating a configuration example of the HMI in a case where processing circuitry is a CPU.

DETAILED DESCRIPTION

[0022] A diagnostic tool and a method for diagnosis will be described with reference to the drawings. There is a case where the same reference numerals will be assigned to the same or corresponding components, and repetitive description will be omitted. Note that there is a case where simple description of the PLC may indicate both the PLC and the safety PLC.

[0023] FIG. 1 is a perspective view of a diagnostic tool 10 according to an embodiment. According to one example, the diagnostic tool 10 includes an attaché case 12. The attaché case 12 includes a handle 12a, which allows a worker to easily carry the attaché case 12. According to one example, the diagnostic tool 10 includes a power supply switch 14 and an AC power supply receptacle 16. According to one example, the AC power supply receptacle 16 can be used as an international electrotechnical commission (IEC) connector for power supply. This enables easy connection to power supplies in each country by only preparing a cable complying with specifications in each country.

[0024] According to one example, the diagnostic tool 10 includes a USB port 18 and a LAN port 20. Further, the diagnostic tool 10 includes an HMI 22. According to one example, the HMI 22 is a touch panel. According to one example, an angle of the touch panel can be adjusted in multiple steps into an angle at which a user can easily view the touch panel. According to another example, the HMI includes a display, a mouse and a keyboard. The USB port 18 described above is, for example, configured to allow storage of data displayed at the HMI 22 in a USB memory which is an external memory. Specifically, the data displayed at the HMI 22 can be stored in the USB memory through operation of the HMI 22 by the USB port 18 being connected to the HMI 22 with wiring. By storing the data in the USB memory, the data can be provided to an engineer outside the factory, and technical advice can be received from the engineer.

[0025] According to one example, the diagnostic tool 10 in FIG. 1 is configured to be incapable of wireless communication. In other words, the diagnostic tool 10 does not have a wireless communication function. As a result of a wireless communication function being not provided, the diagnostic tool 10 can be brought into a customer's factory.

[0026] FIG. 2 is a perspective view of the attaché case 12 in a closed state. In the attaché case 12, for example, the LAN port 20, the HMI 22, a CPU, and the like, are accommodated. According to one example, a total weight of the attaché case 12 and all apparatuses inside the attaché case 12 is made equal to or less than 10 kg, so that a worker can easily carry the attaché case 12 with the handle 12a.

[0027] FIG. 3A is a plan view of inside of the attaché case 12. For example, the HMI 22 is a touch panel of approximately 9 inches. According to one example, the HMI 22, the power supply switch 14, the AC power supply receptacle 16, the USB port 18 and the LAN port 20 are attached to one mounting board 25. Then, the mounting board 25 is fixed to the attaché case 12 with a plurality of screws 23.

[0028] FIG. 3B is a cross-sectional diagram on a line 3B-3B′ in FIG. 3A. The mounting board 25 is fixed to the attaché case 12 by the screws 23 being fastened to thread grooves provided at the attaché case 12.

[0029] FIG. 3C is a cross-sectional diagram on a line 3C-3C′ in FIG. 3A. FIG. 3C illustrates a DC power supply apparatus 24. The DC power supply apparatus 24 enables power supply to the HMI 22, and the like. The DC power supply apparatus 24 is, for example, an AC-DC conversion circuit that supports an input voltage from to 265 V. Further, a fuse 26 is connected to the power supply apparatus 24.

[0030] FIG. 4 is a view illustrating a connection example of the diagnostic tool 10. As illustrated in FIG. 4, the HMI 22 becomes available by connecting a power supply cable 42 to the AC power supply receptacle 16. According to one example, the power supply cable 42 is connected to a power supply of an AC 85 to 264 V and equal to or less than 2 A. According to one example, a memory that stores a program is attached to a back side or inside of the HMI 22.

[0031] For example, an Ethernet cable 40 connects the LAN port 20 and a PLC 34. A safety PLC 36 is disposed next to the PLC 34. According to one example, the PLC 34, the safety PLC 36 and other apparatuses are accommodated in an ELEC BOX 32. The safety PLC 36 is connected to the PLC 34, so that the PLC 34 and the safety PLC 36 can be connected to the diagnostic tool 10 with one Ethernet cable 40. According to one example, the PLC 34 can be connected to the HMI 22 using a hot connect function via the Ethernet cable 40. By connection using the hot connect function, the diagnostic tool 10 can start a diagnosis by connecting the Ethernet cable to the PLC 34 or the Ethernet cable 40 can be unplugged from the PLC 34 without turning off power of the PLC 34 and the safety PLC 36. Thus, the connection using the hot connect function enables execution of respective kinds of processing which will be described later by connecting the diagnostic tool 10 to the PLC in a state where an alarm is detected without turning off power of the PLC.

[0032] FIGS. 5 to 10 are examples of a screen to be displayed at the HMI 22. First, the diagnostic tool 10 is connected to the PLC 34. Then, a top menu screen in FIG. 5 is displayed at the HMI 22. According to one example, the top menu screen is a configuration screen including the PLC and equipment connected to the PLC. In other words, the top menu screen is a configuration screen of equipment incorporated into an apparatus to be diagnosed. FIG. 5 illustrates one CPU unit, and NODEs 2, 3, 4 connected as slaves. According to one example, by the user touching one of the equipment displayed on the screen in FIG. 5, a state of I/O of the touched equipment can be displayed at the HMI 22.

[0033] For example, when the user touches CPU UNIT (ELEC BOX) in FIG. 5, the screen in FIG. 6 is displayed at the HMI 22. In FIG. 6, I/O of the equipment connected to the CPU unit is displayed. In a unit of SI101, buttons of Equipment Front End Module (EFEM) LEFT DOOR and EFEM RIGHT DOOR are not displayed in green, and thus, it can be understood that these sensors are in an OFF state.

[0034] It can be seen from a unit in SI103 that a sensor of N2 KEY SW for which a button is not displayed in green is in an OFF state, and a sensor of Fan Filter Unit (FFU) ALARM for which a button is displayed in green is in an ON state. In this manner, each of SI101, SI102, SI103, SO101, SO102 and SO103 becomes one unit, and ON/OFF states of sensors in each unit can be confirmed.

[0035] In this manner, by selecting the PLC or the equipment displayed on the configuration screen, a state of the PLC or the equipment can be displayed. In other words, an internal state of the PLC can be displayed at the HMI 22. The diagnostic tool 10 is configured to display an internal state of the PLC connected to the LAN port at the HMI 22. According to one example, the internal state of the PLC can be confirmed only by connecting the diagnostic tool 10 to the PLC with the Ethernet cable. Note that the equipment to be connected to the PLC includes, for example, at least one of a sensor, a switch, a motor or a lamp. In this case, the PLC controls the motor or the lamp by reading information of the sensor or the switch and executing a program determined in advance.

[0036] According to one example, a button (hereinafter, referred to as a hidden button) that is invisible to the user can be provided on the configuration screen in FIG. 5. The hidden button is a button for forcedly performing operation performed at the PLC. By making the hidden button a button that is invisible to the user, it is possible to prevent such forced operation from being easily executed. A person who knows existence of the hidden button by a manual, or the like, can forcedly operate the equipment by depressing the hidden button on the touch panel.

[0037] For example, a “hidden button that exists at the HMI and is invisible to the user” is disposed in an upper right region within the configuration screen in FIG. 5. A forced operation screen for forcedly operating the equipment connected to the PLC can be displayed by the user depressing this hidden button using a method determined in advance. According to one example, by making settings such that the screen transitions to the forced operation screen only in a case where the hidden button is successively depressed a predetermined number of times, it is possible to prevent the screen from easily transitioning to the forced operation screen. According to another example, the screen can transition to the forced operation screen only by a plurality of hidden buttons being depressed in order determined in advance. By a method for operating the hidden button being stored as procedures, the user can refer to the procedures as necessary.

[0038] FIG. 7 is a view illustrating an example of the forced operation screen. The user can forcedly operate the equipment by operating the forced operation screen. For example, the user can forcedly operate the equipment by touching part of the forced operation screen. Examples of the forced operation are as follows. [0039] Light an LED, which is not lighted unless an error occurs, by depressing a button on the forced operation screen even if an error does not occur. [0040] Forcedly move a gate valve (GV). For example, open/close the GV to confirm operation when the apparatus is assembled. [0041] Open an EFEM door in a state where a robot operates in the EFEM. Normally, opening of the EFEM door while the robot is operating is not allowed because it is dangerous. [0042] Forcedly issue a signal for discharging an N2 gas.

[0043] The forced operation is not limited to the above-described operation and can include all kinds of operation performed at the PLC. It is therefore possible to perform a number of other kinds of forced operation. According to one example, the apparatus is confirmed before shipment by executing all the forced operation once before the apparatus is delivered. According to one example, operation of all kinds of equipment to be controlled by a transfer module controller (TMC), that is, a transfer system is confirmed through the forced operation. By this means, it is possible to easily confirm that the apparatus normally operates before the apparatus is delivered to a client. Note that such operation could not be performed unless complicated procedures had been performed in related art.

[0044] By the way, for example, in the semiconductor manufacturing apparatus, various interlocks are set by the safety PLC. According to one example, it is possible to confirm whether the interlocks normally function with the diagnostic tool 10.

[0045] An INTERLOCK button is provided in an upper left part of the configuration screen in FIG. 5. By the user depressing the INTERLOCK button, an interlock display screen in FIG. 8 can be displayed at the HMI 22. According to another example, by operating the HMI 22, states of the interlocks of the equipment connected to the PLC can be displayed at the HMI 22.

[0046] It can be said that the interlock display screen in FIG. 8 is a screen in which signals displayed in FIGS. 5 to 7 are collected for each interlock. A list of signals to be used in one interlock is displayed in the interlock display screen in FIG. 8. For example, in a unit of FE Robot Operation Interlock, conditions for allowing operation of a front-end robot are collected. Specifically, the operation of the front-end robot is allowed if all conditions of EFEM Left Door Close, EFEM Right Door Close, LL1 Lid Close and LL2 Lid Close are satisfied. In the example in FIG. 8, red buttons are lighted in all the interlocks, and thus, all the equipment is in an interlocked state and cannot be operated. On the other hand, when green buttons are displayed, the equipment can be operated. In this manner, whether or not the interlocks normally function can be displayed at the HMI 22. According to one example, there are often a number of interlocks, and thus, the interlock display screen may include, for example, 30 or more pages.

[0047] The configuration screen in FIG. 5 includes a button displayed as ALM. According to one example, by displaying the ALM button in red in a case where an alarm is issued, the user can be notified of issuance of the alarm. By the user depressing the ALM button, an alarm list issued from the PLC can be displayed at the HMI 22. FIG. 9 is a view illustrating an example of an alarm list display screen. It can be seen from this alarm list that 10 Minor Faults occur. According to one example, a “Screen Shot” button and a “Send to USB” button can be provided on the alarm list display screen. When the user depresses the Screen Shot button, a screen shot is to be stored in a memory of the diagnostic tool 10. When the user depresses the Send to USB button, the alarm list is stored in the USB memory connected to the USB port 18.

[0048] If the user touches one of the alarms displayed on the alarm list display screen and depresses a show detail button, the screen transitions to a detailed screen of the alarm. FIG. 10 is a view illustrating an example of the alarm detailed screen. In this manner, by selecting an alarm displayed in the alarm list, details of the alarm can be displayed at the HMI 22. The diagnostic tool 10 is configured to cause the HMI to display details of the alarm of the PLC.

[0049] As described above, it is possible to grasp an internal state of the apparatus, forcedly operate the apparatus and confirm a list and details of alarms using the diagnostic tool 10. Further, the diagnostic tool 10 does not have a wireless function and can be regarded as part of the apparatus including the PLC. Thus, also in a case where a note PC is not permitted to be brought into a customer's factory for security reasons, this diagnostic tool 10 can be brought into the customer's factory. For example, it is often the case that security requirements required at customer's factories may be satisfied by configuring the diagnostic tool 10 to be able to give and receive data to and from the user only via the LAN port and the USB port. Further, the above-described respective kinds of operation can be performed simply and intuitively using the HMI typified by a touch panel. Thus, even a person who does not acquaint himself/herself with a method for operating PLC development software can use the diagnostic tool 10. For example, even in a case where an alarmed problem cannot be solved only by persons in a customer's factory, by storing details of the alarm in a USB memory, it is possible to easily seek advice from engineers outside the customer's factory.

[0050] According to one example, the diagnostic tool 10 includes a processing circuitry for performing all or at least a part of the above functions. In one example, the processing circuitry can perform at least the forced operations described above. The processing circuitry may be dedicated hardware, or may be a CPU (also referred to as Central Processing Unit, central processor unit, processing unit, arithmetic unit, microprocessor, microcomputer, processor or DSP) that executes a program which is stored in a memory.

[0051] FIG. 11 is a block diagram of the HMI 22 in a case where the processing circuitry 70b is dedicated hardware. The HMI 22 includes a receiver 70a, processing circuitry 70b, and an output device 70c. The receiver 70a receives data from the PLC. The processing circuitry 70b corresponds to, for example, single circuitry, composite circuitry, a programmed processor, a parallel programmed processor, an ASIC, an FPGA, or a combination thereof. The functions of the diagnostic tool 10 may be realized by the respective pieces of processing circuitry, or the functions may be collectively realized by the processing circuitry. According to one example, the processing circuitry functions as a controller that controls the forced operations. The output device 70c may be the touch panel. In this case, the output device 70c also functions as a input device for receiving instructions from user.

[0052] FIG. 12 is a block diagram illustrating a configuration example of the HMI 22 in a case where processing circuitry is a CPU. In this case, the above series of processes is controlled by a program. For example, a procedure for the forced operations starts automatically. When the processing circuitry 80b is a CPU as illustrated in FIG. 12, each function of the diagnosis tool is realized by software, firmware, or a combination of software and firmware. The software or the firmware is described as a program, and is stored in a computer-readable storage medium 80c. In one example, this program causes a computer to display an internal state of an apparatus, display a list of the alarm, display the details of the alarm, and execute forced operations. In another example, this program causes a computer to transmit a command issued from the HMI by a user to a connection destination of the LAN port.