Robot operation terminal

By setting up a built-in login process in each application of the robot operating terminal and using the management application to confirm operation permissions, the problem of not being able to identify operators in the prior art is solved, and the security of the robot operating terminal is improved, ensuring that only authorized operations are allowed is ensured. Only those who perform specific functions can perform.

CN112989296BActive Publication Date: 2024-11-05DENSO WAVE INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202011474264.2
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2019-12-16
Filing Date
2020-12-14
Publication Date
2024-11-05
Estimated Expiration
2040-12-14

AI Technical Summary

Technical Problem

Existing robot operation terminals cannot effectively identify and confirm the operator's operating permissions when executing applications with different functions, resulting in insufficient security.

Method used

Set up a built-in login process in each application to confirm the operator's operation permissions, and determine whether the operator has the permission to operate the corresponding application by managing the application before starting the application, ensuring that only operators with the appropriate permissions can Perform specific functions.

Benefits of technology

It improves the security of the robot operating terminal, ensures that only authorized operators can operate the robot, reduces the risk of malicious or incorrect operations, and enhances operational security.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN112989296B_ABST
    Figure CN112989296B_ABST
Patent Text Reader

Abstract

The robot operation terminal includes a plurality of applications. The robot operation terminal is connected to a controller that controls the robot, and the robot operation terminal receives input operations performed by an operator to operate or set the robot. In each application, the necessity of a built-in login is set to confirm the operator's operation authority. The robot operation terminal can improve the operational safety of the robot.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to a robot operation terminal that receives an operation performed by an operator to operate a robot. Background Art

[0002] Conventionally, there is known a robot operation terminal such as a teaching pendant. Summary of the invention

[0003] The robot operation terminal includes a plurality of applications. The robot operation terminal is connected to a controller that controls the robot, and the robot operation terminal receives input operations performed by an operator to operate or set the robot. In each application, the necessity of a built-in login is set to confirm the operator's operation authority. BRIEF DESCRIPTION OF THE DRAWINGS

[0004] The objects, features and advantages of the present disclosure will become apparent from the following detailed description made with reference to the accompanying drawings. In the accompanying drawings:

[0005] Figure 1 is a functional block diagram showing the configuration of a robot control system of an embodiment of the present disclosure;

[0006] Figure 2 is a diagram showing different examples of application programs installed in an operation terminal;

[0007] Figure 3 is a flowchart showing the main process executed by the operation terminal.

[0008] Figure 4 is a diagram showing an example of an initial display of an operation terminal displayed after the operation terminal is powered on and activated;

[0009] Figure 5 is a diagram showing another example of an initial display of the operation terminal displayed after the operation terminal is powered on and activated;

[0010] Figure 6 is a diagram showing another example of an initial display of the operation terminal displayed after the operation terminal is powered on and activated;

[0011] Figure 7 is a diagram showing another example of an initial display of the operation terminal displayed after the operation terminal is powered on and activated;

[0012] Figure 8 is a diagram showing a display screen displaying startup applications in a list type for selection by an operator;

[0013] Fig. 9 is a diagram showing a display screen displaying a startup application in a monitor type for selection by an operator; and

[0014] Fig.10 It is a diagram showing an enlarged view of the status bar. DETAILED DESCRIPTION

[0015] Recently, robot operation terminals such as teaching pendants have improved processing capabilities, high communication speeds, high resolution of images displayed on screens, and have become more multifunctional as multiple applications are installed. For industrial robots adopted as production equipment in factories, etc., in order to prevent the robots from damaging items located around the robots and to ensure personal safety, malicious operations or erroneous operations need to be avoided.

[0016] In addition, the role of the operator is different at each stage of the industrial robot product life cycle, such as development, manufacturing, application by system integrators for specific purposes, field operation, maintenance, and research. In the case of a robot operating in a production site, an unspecified number of operators can operate the robot using an operation terminal.

[0017] As described above, the robot operation terminal has various requirements. From the perspective of ensuring safety, in some robot operation terminals, before inputting operations into the robot operation terminal, the operation terminal identifies the operator or the operator's operation authority through a login process similar to a personal computer.

[0018] However, there are two types of current robot operation terminals. One is an operation terminal that requires a login process, and the other is an operation terminal that does not require a login process. When executing applications with different functions, the current robot operation terminal cannot identify the appropriate operator.

[0019] The present disclosure has been made in view of the above-mentioned difficulties, and an object of the present disclosure is to provide a robot operation terminal capable of identifying an appropriate operator when executing various application programs.

[0020] According to one aspect of the present disclosure, a robot operation terminal includes a plurality of applications. The robot operation terminal is connected to a controller that controls a robot, and the robot operation terminal receives input operations performed by an operator to operate or set up the robot. In each application, the necessity of a built-in login is set to confirm the operator's operating authority.

[0021] With this configuration, after confirming the necessity of the operation authority according to the function of the application, the operator is permitted to operate the corresponding application. This configuration improves the safety of the operation terminal when the robot is operated using the operation terminal.

[0022] The application program may include a predetermined application that is activated as a startup application immediately after the robot operation terminal is powered on.

[0023] With this configuration, when the application is started without requiring the operator to perform built-in login, the operator can immediately execute the application. When the application requires the operator to perform built-in login, the application is executed after safety is confirmed by performing built-in login.

[0024] The predetermined application started as the startup application may not require built-in login by the operator, and enables the operator to instruct basic operations to the robot.

[0025] By setting the operation terminal application as the startup application, the operator can immediately operate the robot at the site of the robot without performing built-in login.

[0026] The robot operation terminal may further include a management application that manages a process executed in response to activation of an application. The management application is configured to be activated before starting the application in response to an input operation performed by an operator. The management application performs a management login that confirms the operation authority of the operator. The management application also determines whether the operator has the operation authority to operate one of the applications selected by the operator.

[0027] In response to determining that the operator has the operation authority, the management application transfers the process to one of the applications selected by the operator. In response to determining that the operator does not have the operation authority, the management application performs management login before transferring the process to one of the applications selected by the operator. In the case that one of the applications selected by the operator requires a built-in login, the management application instructs the operator to perform the built-in login.

[0028] With this configuration, the operator's operating authority can be confirmed only through the management login of the management program. Alternatively, the operating authority can be confirmed in two stages: the management login in the management program and the built-in login of the application selected by the operator. In the configuration in which the operator's operating authority is confirmed only through the management login of the management program, the operator who has confirmed the operating authority through the management login can cancel the subsequent built-in login of the selected application. Further, by confirming the operating authority in two stages, the operational safety of the robot can be further improved.

[0029] The application may include one or more built-in logins that also have different levels of operational permissions required during execution of the application.

[0030] With this configuration, in the case where a plurality of functions are executed by one application, the operation authority of the operator can be confirmed before execution according to the content of each function.

[0031] Applications that also require one or more built-in logins can have three different levels of operating permissions.

[0032] In a configuration in which the operation authority of an operator is set in three or more stages, a required level of the operation authority can be appropriately set according to the function of the application.

[0033] The robot operation terminal may further include a display screen that displays a status bar in a predetermined portion of the display screen. The status bar displays operation items for switching the operation state of the robot and status information items related to the robot using symbols.

[0034] With this configuration, the operator can be informed of the operating state of the robot by referring to the status bar during the operation of the robot. The operator can easily change the operating state of the robot by operating the displayed operation items.

[0035] According to another aspect of the present application, a robot operation terminal includes a processor and a memory in which a plurality of applications are installed. The application is executed by the processor. The robot operation terminal is connected to a controller that controls the robot and receives an input operation performed by an operator to operate or set the robot. In each application, the necessity of a built-in login is set to confirm the operator's operation authority.

[0036] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. Figure 1 As shown, the robot control system 1 according to the present embodiment includes a robot 2, an operation terminal 3 connected to the robot 2, and an external device 4 connected to the robot. The robot 2 includes a robot body and a controller for controlling the robot body. The controller of the robot 2 is installed with a robot control application 5, which is an application for controlling the robot 2. Hereinafter, an application is also referred to as an application or an app.

[0037] The operation terminal 3 is installed with an operation terminal application 6 and other optional applications 7 to 9. The optional applications 7 and 8 are applications capable of operating the robot 2. The optional application 7 is connected to the external device 4, and controls the external device 4, and receives a signal transmitted from the external device 4. The optional application 8 is not connected to the external device 4. The operation terminal application 6 allows the operator to change the settings of the operation terminal 3, and instructs the operator to perform basic and simple operations of the robot 2. Further, a management application 10 is installed in the operation terminal 3. The management application 10 manages the processes executed by the other applications 6 to 9, and corresponds to a management program.

[0038] The operation terminal 3 may include a processor 31 for executing an application and a memory 32. The application is installed in the memory 32 and executed by the processor 31 to perform a corresponding function.

[0039] The external device 4 includes, for example, a camera 11, a sensor 12, and an actuator 13. The camera 11, for example, obtains image information required to operate the robot 2, and inputs the image information to the controller of the robot 2. Similarly, the sensor 12 obtains sensing information required to operate the robot 2, and inputs the sensing information to the controller of the robot 2. The actuator 13 is, for example, a servo motor, which is a control object other than the robot 2. The external device 4 including the above-mentioned components is controlled by the robot control application 5. The communication of each signal between the robot 2, the operation terminal 3, and the external device 4 is performed by the physical connection line shown in the figure or by the circuit line.

[0040] In addition, despite Figure 1 Four applications 6 to 9 are shown as an example, but the number of application programs actually installed in the operation terminal 3 may be greater than four. Figure 2 A plurality of applications classified into different categories are shown. In the present embodiment, a built-in login process is set in each application. For an operator operating the operation terminal 3, for example, four levels of authority including level 1 to level 4 are set as follows. Level 1 is the lowest authority level.

[0041] 1. Operator

[0042] 2. Programmer

[0043] 3. Maintenance personnel

[0044] 4. Administrator

[0045] The operator is a person who does not need to log in to the operation terminal 3. Programmers, maintenance personnel, and administrators all need to log in to the operation terminal 3. Hereinafter, the operator may also be referred to as a user.

[0046] The operator can execute the operation terminal application 6 and the application 21 without performing the built-in login process of the application. In order to execute the application 22, the built-in login process needs to be executed. The four stages in the application 22 indicate that four different login processes need to be executed to execute the application 22 to four different stages. Hereinafter, the built-in login process may also be referred to as a built-in login. The login performed by the management application 10 is referred to as a management login.

[0047] In addition to the above-mentioned applications that can be executed by the operator, the programmer can also execute applications 23 to 25. Application 23 can be executed without a built-in login process, and applications 24 and 25 require the execution of a built-in login process. Similar to application 22, in order to execute application 25 to four different stages, four different login processes need to be executed as shown in the four stages.

[0048] In addition to the applications that can be executed by the programmer, the maintenance personnel can also execute applications 26 and 27. Application 26 can be executed without a built-in login process, and application 27 requires the execution of a built-in login process. In order to execute application 27 into two different stages, two different login processes need to be executed as shown in the two stages in the figure.

[0049] In addition to the applications that can be executed by the maintenance personnel, the administrator can also execute applications 28 to 30. Application 28 can be executed without a built-in login process, and applications 29 and 30 require the execution of a built-in login process. Similar to application 22, in order to execute application 30 to four different stages, four different login processes need to be executed as shown in the four stages.

[0050] The operation of the operation terminal according to this embodiment will be described below. Figure 3 In FIG. 1 , “TP” is an abbreviation of “teaching pendant” and is an example of the operation terminal 3. Figure 3 As shown, in response to the power-on of the operation terminal 3, the management application 10 is first started in S1, and then the predetermined application set in advance is started by selection in S2. Under the condition that the user does not change the setting, usually, the operation terminal application 6 is started in S2.

[0051] When no changes are made to the startup application (as the application started in S2) (S3: No), the management application 10 proceeds to S7. When changes are made to the startup application (S3: Yes), the operation terminal determines in S4 whether the current user has the operating authority to make changes, for example, risk assessment authority. The current user is the user who previously operated the operation terminal 3, unless the startup application is changed. When the current user does not have the operating authority to the startup application (S4: No), the process proceeds to S7. When the current user has the operating authority to the startup application (S4: Yes), in S5 the operation terminal receives the new startup application selected by the user, and in S6 the management application 10 changes the current startup application to the new startup application. The new startup application will be started from the next boot.

[0052] In S7, in response to a user change, that is, a user different from the last user (S7: Yes), the user selectively performs a management login operation on the management application 10 in S8 and S9, and changes the user in S10. Then, the process proceeds to S11. In S7, in response to no user change (S7: No), the process proceeds from S7 to S11.

[0053] When the user selects to execute the function of the launch application in S11 (S11: Yes), the management application 10 determines in S12 whether the operation permission is required for the function. The function is not limited to all functions executed by the launch application. In the case where the launch application is configured to selectively execute part of the functions, the operation permission can be determined for the function selected by the user among the multiple functions. In response to determining that the function to be executed requires the operation permission (S12: Yes), the management application 10 instructs the user to perform management login in S13.

[0054] As a default startup application, for user convenience, an operation terminal application 6 that does not require a built-in login process and allows the operator to instruct basic operations of the robot can be set. By setting the operation terminal application as a startup application, the operator can immediately operate the robot 2 at the site of the robot 2 without executing the built-in login process.

[0055] In S14, the management application 10 hands over the process to the startup application to execute the function of the startup process. In the case where the startup application requires a built-in login to execute all or part of the functions of the startup program, the built-in login process is executed in S14. Then, the process proceeds to S15. In S11, when the user does not execute the function of the startup application (S11: No), the process proceeds from S11 to S15.

[0056] When the user chooses to switch applications in S15 (S15: Yes), the management application 10 determines in S16 whether the operation permission is required for the function of another application to which the user switches. In response to determining that the operation permission is required (S16: Yes), the management application 10 instructs the user to execute the management login process in S17, and switches the application in S18. Then, the process is handed over to the application after the switch. In the case where the switched application requires a built-in login to execute all or part of the functions of the application, the built-in login process is executed in S18. After that, the user continues the operation of the operating terminal 3 (S19: No), and the process returns to S3.

[0057] Figure 3 The processing when it is determined that the user does not have the operation authority as a result of each login process is not shown. In this case, for example, a login based on another user can be requested, or the operation of the operation terminal 3 can be stopped.

[0058] By performing control as described above, the login process in the operation terminal 3 of this embodiment has the following four login modes.

[0059] (1) Not logged in

[0060] (2) Built-in login only

[0061] (3) Administrative login only

[0062] (4) Built-in login and management login

[0063] Login modes (1) and (2) are suitable for applications having functions independent of the robot 2 and to be used in the operation terminal 3. For example, login modes (1) and (2) are suitable for product support software that manages tables and edits documents.

[0064] The login mode (3) is suitable for applications having functions to be used included in the functions of the robot 2. For example, the login mode (3) is suitable for software having control functions of the robot 2, such as a mode switching function or a control program of the robot 2.

[0065] The login mode (4) is suitable for applications having functions partially overlapping with some functions of the robot 2. For example, the login mode (4) is suitable for software having a control function of the external device 4, such as changing settings of the camera 11 or the sensor 12.

[0066] Figures 4 to 7 is a diagram showing an example of an initial display image displayed on the display screen 33 of the operation terminal 3 after the operation terminal 3 is powered on and activated. Figure 4 This is an initial display of a preview type, in which the names of applications 1 to 6 are displayed on the left and a preview of the currently selected application 1 is displayed on the right. As a preview of the selected application, the functions of the selected application can be displayed. In the preview display, a large amount of information about the application can be displayed.

[0067] Figure 5 This is the initial display of the list type. In this initial display, only Figure 4 The list shown is displayed on the left side of the initial display. Figure 6 It is the initial display of the monitor type. In this initial display, the entire display image is divided into 6, for example, to display the names of applications 1 to 6. According to the monitor type, all applications installed in the operation terminal 3 can be presented to the user with good visibility. Specifically, the initial display of the list type can save display space.

[0068] Figure 7 This is the initial display of the carousel type. In this initial display, when the operation terminal has 6 installed applications 1 to 6, the first application 1 is displayed in the center, the second application 2 is displayed on the right, and the sixth application 6, which is the last application, is displayed on the left side of the first application 1. The user operates the cursor to cycle the displayed applications. The initial display of the carousel type is an intermediate display form between the preview type and the list type, and in the carousel type, it is possible to balance the ensuring of the amount of information about the application and the saving of the display space.

[0069] Figure 8 and Fig. 9The display screen of the operating terminal 3 is shown in a more realistic manner. Figure 8 A display screen is shown which displays startup applications in a list type for selection by an operator. Fig. 9 The display screen of the startup application for the operator to select is shown in a monitor type. This is an example of a display screen for the operator to switch applications. The status bar 14 is displayed Figure 8 and Fig. 9 The details of the status bar 14 will be described below.

[0070] like Fig.10 As shown, on the status bar 14 , operation items for switching the operation status of the robot 2 and a plurality of status information items indicating the operation status of the robot 2 are displayed by symbols.

[0071] (1) Mode switching

[0072] An operation item for switching the operation mode between automatic, manual, teach check, remote, and direct.

[0073] (2) Activation Rights

[0074] It is an operation item that can start robot programs such as ANY, Ether, IO, and TP.

[0075] (3) Program execution status

[0076] The program execution status displays the status of the program in the execution state and the stopped state, the privileged tasks in the execution state, the program and privileged tasks in the execution state, the message output, and the vicinity of the singularity.

[0077] (4) I / O settings

[0078] I / O Settings displays settings related to input / output, such as IO lock, pseudo input, and extended functions.

[0079] (5) System operation status

[0080] System operating status displays the operating status of the system, such as error occurrence, warning, and external device connection.

[0081] (6) Hard SW status

[0082] The Hard SW Status displays the setting status of the hardware switches, such as Emergency Stop, Protection Stop, Auto Enable, and Enable Switch.

[0083] (7) Robot name

[0084] The robot hand name displays the name of the robot that is input and specified in advance by the user.

[0085] (8) Job / Tool Number

[0086] The job / tool ​​number shows the job or tool number. For example, W0 indicates the target job assigned the number No.0, and T0 indicates the tool assigned the number No.0.

[0087] (9) Speed

[0088] Speed ​​shows the robot's operating speed in percentage.

[0089] As described above, according to the present embodiment, the operation terminal 3 has a plurality of applications 7 to 9 and 21 to 30, and the necessity of a built-in login process for confirming the operation authority of the operator is respectively set in the applications 7 to 9 and 21 to 30. Therefore, after confirming the necessity of the operation authority according to the functions of the applications 7 to 9, etc., the operator is permitted to operate the corresponding applications 7 to 9, etc. This configuration improves the safety of the operation terminal 3 when the robot 2 is operated using the operation terminal 3.

[0090] The operation terminal 3 is installed with an application management application 10, which manages processes executed in response to the execution of applications 7 to 9, etc. In response to the operation terminal 3 being started and the operator starting to input an operation, the management application 10 is first started. The management application 10 instructs the operator to execute a management login process for confirming the operator's operation authority. Subsequently, when the operator selects an application and the selected application is executed, the management application determines whether the operator has the operation authority for the selected application.

[0091] In response to determining that the operator has the operating authority, the management application 10 transfers the process to the selected application. In response to determining that the operator does not have the operating authority, the management application 10 executes the management login process and then transfers the process to the selected application. In the case where the application to which the process is transferred requires a built-in login, the operator is instructed to execute the built-in login process. Through this configuration, the operating authority of the operator can be confirmed only through the management login process of the management application. Alternatively, the operating authority can be confirmed in two stages, the management login process in the management application 10 and the built-in login process of the selected application. In the configuration of confirming the operating authority of the operator only through the management login process of the management application, the operator who has confirmed the operating authority through the management login process can cancel the subsequent built-in login process of the selected application. Further, through the two-stage confirmation of the operating authority, the operational safety of the robot can be further improved.

[0092] Among the applications 21 to 30, the applications 22, 25, and 30 require one or more built-in login processes with different operation privileges in the execution of the application programs. With this configuration, in the case where a plurality of functions are executed by one application 22 or the like, the operation authority of the operator can be confirmed before execution according to the content of each function. In the configuration in which the operation authority of the operator is set in four stages, the required level of the operation authority can be appropriately set according to the function of the application program.

[0093] The operation terminal application 6 is set as a default startup application. By setting the operation terminal application 6 as a startup application, the operator can immediately operate the robot 2 at the site of the robot 2 without executing a built-in login process.

[0094] The operation terminal 3 displays a status bar 14 in which operation items for switching the operation state of the robot 2 and a plurality of status information items indicating the operation state of the robot 2 are displayed by symbols. The status bar 14 is displayed at a predetermined portion of the display screen, for example, at an upper end portion of the display screen. With this configuration, the operator can be informed of the operation state of the robot 2 by referring to the status bar 14 during the operation of the robot 2. The operator can easily change the operation state of the robot 2 by operating the displayed operation items.

[0095] The present disclosure is not limited to the embodiments described above or shown in the drawings, and may be modified or expanded as follows.

[0096] In response to the activation of the operation terminal 3, the program that is first activated is not limited to the management application 10. Other applications 7 to 9, 21 to 30, etc. may be set to be activated first after the operation terminal is powered on, according to the operator's selection.

[0097] The items displayed in the status bar 14 are not limited to the above items (1) to (9). Different items can be selected as needed to be displayed in the status bar 14. The number of items displayed in the status bar is not limited to ten. The number can be greater or less than ten.

[0098] The display portion of the status bar 14 may be the lower end, the left end, or the right end of the display screen. The display portion of the status bar 14 may be both sides of the upper end and the lower end of the display screen, both sides of the left end and the right end of the display screen, or may be along the four ends of the display screen. The status bar 14 may be displayed only when the status bar 14 is needed. That is, when the status bar is not needed, the status bar 14 is not displayed.

[0099] The level of operation authority can be set appropriately as needed. For example, a risk assessor with a higher level than an administrator can be set, and the operation terminal has five levels of authority.

[0100] In response to the operation terminal being powered on, all applications installed in the operation terminal may be started.

[0101] At the beginning of the application execution, the built-in login process may not be required. Alternatively, the built-in login process may be required in response to the execution of a function requiring operation authority within the application.

[0102] The application started first may be an application preset by the manufacturer. In this configuration, even if an abnormality occurs in the operation terminal 3, an application that can safely stop the robot 2 may be set with a higher priority. The application may safely stop the robot 2 based on the monitoring result of the robot 2 by the controller of the robot 2.

[0103] The startup applications may be assigned a predetermined priority order. For example, the priority order may be set in the order described based on (i) manufacturer applications for operating the robot, (ii) manufacturer applications such as easy vision picking (EVP) and origin return, and (iii) applications selected by the user. For example, the criteria for setting the priority may be based on CPU priority, core allocation in the case of a multi-core configuration, communication restrictions, process monitoring, etc.

[0104] Multiple applications can be executed simultaneously. For example, if the screen has a sufficiently high switching speed, the operations corresponding to each application can be executed in the background. Each application can be terminated and restarted separately.

[0105] The application management application 10 manages each application by monitoring the process. The monitoring targets include, for example, CPU load rate, memory usage, existence confirmation, whitelist, etc.

[0106] In the execution of multiple applications, the control of each application is independent of each other, and the adverse effects caused by other applications are eliminated as much as possible.

Claims

1. A robot operation terminal, comprising: Multiple applications (6 to 9, 21 to 30); as well as a management application (10) that manages processes executed in response to activation of the plurality of applications, wherein The robot operation terminal is connected to a controller for controlling the robot; The robot operation terminal receives an input operation performed by an operator to operate or set the robot; and In each of the plurality of applications, necessity for a built-in login is set for confirming the operation authority of the operator, in, The plurality of application programs include a predetermined application (6) which is immediately started as a startup application after the robot operation terminal is turned on. in, The management application is configured to be activated before the launch application in response to the input operation performed by the operator; The management application executes management login to confirm the operation authority of the operator; The management application further determines whether the operator has an operating authority to operate one of the plurality of applications selected by the operator; In response to determining that the operator has the operation authority, the management application transfers the process to the one of the plurality of applications selected by the operator; In response to determining that the operator does not have the operation authority, the management application performs the management login before handing over the process to the one of the plurality of applications selected by the operator; and In a case where the one of the plurality of applications selected by the operator requires the built-in login, the management application instructs the operator to execute the built-in login.

2. The robot operation terminal according to claim 1, wherein: The predetermined application started as the startup application does not require the built-in login of the operator, and enables the operator to instruct basic operations to the robot.

3. The robot operation terminal according to claim 1, wherein: The plurality of applications include applications (6, 22, 24, 25, 27, 29, 30), and the applications (6, 22, 24, 25, 27, 29, 30) also require one or more built-in logins with different operating authority levels during the execution of the applications.

4. The robot operation terminal according to claim 3, wherein: It is also required that one or more of the applications (6, 22, 25, 30) with built-in logins have more than three different operating authority levels.

5. The robot operation terminal according to any one of claims 1 to 4, further comprising: a display screen (33), wherein the display screen (33) displays a status bar on a predetermined portion of the display screen, The status bar uses symbols to display operation items for switching the operation status of the robot and status information items related to the robot.

6. A robot operation terminal, comprising: Processor(31); as well as a memory (32), in which a plurality of application programs (6 to 9, 21 to 30) are installed, and the plurality of application programs are executed by the processor, in, The robot operation terminal is connected to a controller that controls the robot. The robot operation terminal receives an input operation performed by an operator to operate or set the robot, and In each of the plurality of applications, necessity for a built-in login is set for confirming the operation authority of the operator, in, The plurality of application programs include a predetermined application (6) which is immediately started as a startup application after the robot operation terminal is turned on. in, In addition to the plurality of applications, a management application (10) is installed in the memory. the management application manages processes executed in response to activation of the plurality of applications; The management application is configured to be activated before the launch application in response to the input operation performed by the operator, The management application performs management login to confirm the operation authority of the operator, The management application further determines whether the operator has an operation authority to operate one of the plurality of applications selected by the operator, In response to determining that the operator has the operation authority, the management application transfers the process to the one of the plurality of applications selected by the operator, In response to determining that the operator does not have the operation authority, the management application performs the management login before handing over the process to the one of the plurality of applications selected by the operator, and In a case where the one of the plurality of applications selected by the operator requires the built-in login, the management application instructs the operator to execute the built-in login.

7. The robot operation terminal according to claim 6, wherein: The predetermined application started as the startup application does not require the built-in login of the operator, and enables the operator to instruct basic operations to the robot.

8. The robot operation terminal according to claim 6, wherein: The plurality of applications include applications (6, 22, 24, 25, 27, 29, 30), and the applications (6, 22, 24, 25, 27, 29, 30) also require one or more built-in logins with different operating authority levels during the execution of the applications.

9. The robot operation terminal according to claim 8, wherein: The applications (6, 22, 25, 30) also require one or more built-in logins with three different operating permission levels.

10. The robot operation terminal according to any one of claims 6 to 9, further comprising: a display screen (33), wherein the display screen (33) displays a status bar on a predetermined portion of the display screen, The status bar uses symbols to display operation items for switching the operation status of the robot and status information items related to the robot.