Patent Application
20210039254
The present invention relates to a method for programming an industrial robot. More specifically, the invention relates to 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. The invention provides a software platform, where the developer can define customized installation screens and program nodes for the end user.
Before an industrial robot is to be put in operation for a certain task, it must be programmed to carry out the task. Various robot programming languages are available originating from different robot suppliers. A robot program comprises a series of robot instructions written in a robot programming language.
Customers who buy industrial robots generally want to be able to control or manipulate a robot, and to program the robot, relative to various objects and boundaries in the surroundings of the robot, such as machines, objects or blanks, fixtures, conveyers, pallets or vision systems.
The end-user would sometimes face a challenge when installing and programming third party hardware (tools, such as grippers) as well as accompanying third party software to be integrated in the industrial robot system.
Industrial robots are highly flexible devices used for a wide variety of operations in many different industrial applications. Industrial robots are conventionally programmed via a robot programming language that is very similar to conventional computer programming languages. A robot program includes a sequence of program instructions, where each instruction tells the robot control unit what to do and how to do it. Robots are programmed to follow a path including a plurality of target points. The robot program includes the positions of the target points. The programming of robots is a time consuming process and the conventional methods of using the robot during the programming and teaching process ties up the production equipment and delays production start.
There is a need for a method to extend 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.
The above and other objects and advantages are obtained by the provision of a programmable robot having the unique feature that it can be programmed with third party plug-ins provided with the third party tools.
Thus, according to a first aspect of the present invention there is provided a method of programming an industrial robot with third party hardware and software, wherein the method includes:
The method may further comprise one or more of the following steps:
According to a further aspect of the invention, the object is achieved by a computer program directly loadable into the internal memory of a computer or a processor, comprising software code portions for performing the steps of the method according to the invention, when said program is run on a computer. The computer program is provided either on a computer readable medium or through a network.
According to another aspect of the invention, the object is achieved by a computer readable medium having a program recorded thereon, when the program is to make a computer perform the steps of the method according to the invention, and said program is run on the computer.
According to the invention, a set of predefined workstations, comprising preprogrammed robot code, are stored in a memory location. The user creates a robot program by selecting one or more workstations from the predefined set of workstations and specifying the order in which the robot shall visit the selected workstations. This allows the operator to create a graphical representation that reflects the configuration of the real robot cell.
A workstation is a physical location on which the robot may carry out work. Each predefined workstation represents a real workstation and a defined task to be carried out by the robot at the workstation. The preprogrammed robot code is specially designed for controlling the robot so that it carries out the defined task at the workstation. Examples of workstations are: an injection mold machine, a dye casting machine, a scrap station for throwing away rejected objects, a device for vision control of the object, one or more stations for subsequent treatment of the object, and an output station such as a conveyer. Examples of tasks are: pick a molded object from the mold, throw the object in the waste basket, hold the object during a vision control, move the object in a predefined way in relation to a treatment tool, put the object in an assembly with other objects, place the object on the conveyer. The subsequent treatment is for instance flaming, deburring, degating, dispensing, polishing, grinding or painting.
The user interacts with one or more graphical interfaces during the creation of the robot program. In this context a graphical interface is defined as a view or a part of a view, adapted for interaction with a user and displayed on the display device. The graphical interface is adapted for displaying information, in the form of text and symbols, and choices to the user, and to receive commands, data and selections entered by the user.
A robot program is generated based on the stored, predefined workstations including predefined robot program code, and information entered by the user via the user interfaces about selected workstations and the order in which the robot shall visit the selected workstations. The programming code is hidden from the user, and the user creates a robot program by interacting with one or more graphical interfaces. Thus, the invention makes it possible for a user to create a robot program without using any programming code. The invention offers an easy and pedagogical way to program a robot, and does not require any knowledge about robot languages. Based on the software platform provided with the present invention it is easy for the user to reprogram the robot in connection with adding and removing a third party workstation to the robot cell. A further advantage gained with the present invention is that the user will find it just as easy to program an advanced robot with five or six axes, as to program a simple linear robot with only three axes. The term industrial robot refers to linearly movable manipulators as well as robots including rotational movement axes. The invention is useful for programming industrial manipulators or robots for any application including visiting and performing work on one or more workstations.
The invention will now be explained more closely by the description of the principles shown in
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.
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.
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.
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.
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).
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.
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.
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.
The framework of the present invention enables:
| Number | Date | Country | Kind |
|---|---|---|---|
| PA 2015 70451 | Jul 2015 | DK | national |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15738315 | Dec 2017 | US |
| Child | 17080213 | US |
