METHOD FOR EXTENDING END USER PROGRAMMING OF AN INDUSTRIAL ROBOT WITH THIRD PARTY CONTRIBUTIONS

Abstract

There is provided a method for programming an industrial robot, where distributors and integrators can present accessories that run successfully at end users. Also the developer can define customized installation screens and program nodes for the end user. There is provided a software platform, where the developer can define customized installation screens and program nodes for the end user thereby extending an existing robot system with customized functionalities by still using the software platform available in the robot system. Hereby a robot developer can define customized installation screens and program nodes for the end user. These can, for example, encapsulate complex new robot programming concepts, or provide friendly hardware configuration interfaces.

Claims

1. A method for an end-user to program an industrial robot with third party hardware and/or software components, wherein the method includes: providing an industrial robot having a graphical user interface (GUI) for programming the robot and installing third party software, said GUI provided with: an installation tab, wherein the installation of the robot is specified, said installation tab configured to allow setting up of parameters for hardware, such as third party hardware, mounted on the robot, and a program tab, wherein the program of the robot is specified, said program tab configured to allow setting up of the steps to be performed by the hardware; installing the third-party software, based on a dedicated file format, that adds a GUI element to the installation tab and/or the program tab; and optionally installing third-party hardware, such as a tool, based on said software components containing GUI elements.

2. Method according to claim 1, wherein the method further comprises storing in a memory location a set of predefined positions comprising preprogrammed robot code to define one or more geometrical features relative to objects in the surroundings of the robot and establishing a relationship between said geometrical features and first coordinates of a robot-related coordinate system

3. Method according to claim 2, wherein the method further comprises integrating the GUI on a graphical display device, displaying information about the predefined positions and allowing a user to select one or more of the predefined positions and to specify the order in which the robot shall visit the selected positions.

4. Method according to claim 3, wherein the method further comprises receiving information about which of the predefined positions the user has selected and the order in which the robot shall visit the selected workstations, and generating a robot program for performing a work cycle based on said predefined positions and said received and stored information about the selected positions and the order in which the robot shall visit the selected positions.

5. Method according to any one of the claims 1-4, wherein the robot has an extensible operating system allowing for third-party daemons, servers and other programs to be installed on the robot controller, to extend the functionality of the robot controller, for use by the added GUI elements.

6. Method according to any one of the claims 3-5, wherein the third-party hardware is an electro-mechanical gripper, said software components containing GUI elements being selected in the installation tab, whereby the end-user is visually informed how the gripper's power supply and communication interface should be connected, after which the gripper boots up and starts communicating with the gripper GUI element of the program tab thereby detecting the physical gripper and the graphical display device shows a configuration interface enabling the end-user to configure one or more physical parameters, such as maximum closing force of the gripper, said method being completed by the end-user when navigating to the program tab programming a task to be performed by the robot by an corresponding program node.

7. Method according to any one of the claims 1-5, wherein the third-party hardware is a vision system, said software components containing GUI elements being selected in the installation tab, whereby the end-user is visually informed how the vision system should be connected to the robots, how camera coordinates relates to robot coordinates, and what parts to identify in the vision system, said software components optionally containing a GUI element of the program tab thereby enabling the programmer of the robot to move to an identified part, where the generated program automatically incorporates the mathematical transformation from vision system coordinates to robot coordinates, thereby removing the requirement of the programmer to understand and being able to handle this complexity inherent to vision guided robotics.

8. Method according to any one of the claims 1-5, wherein the third-party hardware is an interface to other industrial equipment, where the third party elements added to the installation tab would hold information about connecting the robot to the specific other equipment, and at the same time extend the functions in the programming tab to include triggering specific events or functions in the third-party equipment.

9. A programmable robot provided with software for carrying out the method according to any one of the preceding claims 1 to 8.

Description

BRIEF DESCRIPTION OF THE DRAWING

[0022] FIG. 1 shows a diagram of the relationship between the software and hardware components supplied with the robot system and the third-party supplied additions to this system.

DETAILED DESCRIPTION OF THE INVENTION

[0023] The invention will now be explained more closely by the description of the principles shown in FIG. 1. Specifically the FIGURE shows how the programming of an industrial robot with third party hardware and software is carried out. An industrial robot having a user graphical interface (GUI) for programming the robot is provided. The installation of the third party software is performed where the GUI includes an installation tab, wherein the installation of the robot is specified, said installation tab configured to allow setting up of parameters for the third party hardware mounted on the robot, and a program tab, wherein the program of the robot is specified, said program tab configured to allow setting up of the steps to be performed by the hardware. Then the third-party software is installed, based on a dedicated file format that adds a GUI element to the installation tab and the program tab. Finally the third-party hardware (or own hardware) is installed based on said software components containing GUI elements.

[0024] The invention concerns a platform where distributors and integrators can present accessories that run successfully at end users. This gives rise to shorter lead time to implement robot applications, and lower project risks, higher predictability of project costs and time, access to well-proven technology, and share information. The concept includes both hardware and software solutions, whereas the present invention is concerned with the software aspects of this concept.

[0025] By implementation of the present invention an industrial robot becomes receptive to the installation of third-party software components, based on a dedicated file format. These files can amongst other things contain graphical user interface elements that will become part of our user interface. A typical use case could be the installation of a gripper on the robot. The gripper would come with a dedicated file, which would add a general user interface element to the installation tab (where the installation of the robot is specified) and to the program tab (where the program of the robot is specified). In the installation tab, it would allow the set-up of parameters for how the gripper is mounted on the robot and what electrical signals are used for the gripper. In the program tab, it would allow to specify whether the gripper should open or close, and possible also the gripping force, closing speed etc.

[0026] Generally, an industrial robot comprises a manipulator, a control unit for controlling the manipulator, and a portable operator control device, denoted a teach pendant unit, for teaching and manually operating the manipulator.

[0027] In accordance with the present invention end-users have the possibility to install various plugin packages. A single package may contain a contribution to the installation tab and/or program nodes. After installation of the software the new screens will automatically become available for the control device. Furthermore, the screens look and act as if they were part of the default control environment.

[0028] Installation tab contributions store their settings in the, so called, installation. This file contains the configuration for a particular work-cell. The configuration among others contains the verified safety settings. End-users programming robots, using the present invention, automatically link the program under design to the specific installation. Consequently, when the program is loaded, the assigned installation (including verified safety configuration and settings) is loaded as well. This simplifies the workflow for end-users, because the number of significant configuration files remains the same (i.e. one).

[0029] Program node contributions store their parameters in the, so called, program files. These files contain the program for the automation task the robot is supposed solve. The combination of default control program parameters and specific parameters gives the same workflow advantages to the end-user (similar to the installation file), since the number of significant files remains one.

[0030] The separation of concerns, between configuration of the robot work-cell and program design, promoted by the control device lowers the design complexity for end-users. Both concerns focus on complementary aspects of the automation task and give the end-user a systematic way of solving the automation problem. The control device ensures that both concerns are integrated in an appropriate manner. With the framework of the present invention the same separation of concerns and integration can be provided to end-users, i.e. installation tab contributions can share settings with program node contributions.

[0031] For instance, if an electro-mechanical gripper is supposed to be installed and used for an automation task the following steps could be taken. As the gripper supplier chose to guide the end-user through the installation process, he directs the end-user to install the plug-in first and to navigate to the Installation tab. In the Installation tab the contribution then shows the end-user visually how the gripper's power supply and communication interface should be connected. After the communication interface and power have been connected physically, the gripper boots up and starts communicating with the gripper software. At this point, the gripper software detects the physical gripper and the screen changes from showing the visual installation guide to a configuration interface. In the configuration interface, for instance, the maximum closing force can be configured. After the configuration has been done, the end-user can start making a program. The end-user navigates to the program tab and starts programming his task. At the point where he wants to fetch an object he looks for an appropriate program node and finds the Gripper node. He inserts the gripper node in the same manner as any other program node. The command tab (for program node parametrization) shows the available parameters that can be tuned in a visually appealing manner. After the end-user specified the gripper opening distance and closing distance, the gripper node is parameterized. To test the gripper parameters, the command tab offers a Joggle button which will open and close the gripper, without running the entire program. Before any program can be run, each program node will need to generate a code that executes the specified actions. Information stored in the installation, e.g. the maximum closing force, can be employed here as well. For the gripper node, the developer has taken care of the script generation (using the framework of the present invention). On pressing the play button in the control device, the program will be converted into the script of the robot and the robot will start performing the programmed task.

[0032] The framework of the present invention enables: [0033] Easy setup of third party hardware, which is usually a complex task not suited for regular end-users (like factory workers). The benefits are: lower technical expertise required, less time for setup and allows easy repetition for setup of 3.sup.rd party hardware->lower setup costs. [0034] Seamless integration with the normal workflow. [0035] Both the framework and control device promote the same workflow.