US9114528B2 - Control system of a robot - Google Patents

Control system of a robot Download PDF

Info

Publication number
US9114528B2
US9114528B2 US13/548,288 US201213548288A US9114528B2 US 9114528 B2 US9114528 B2 US 9114528B2 US 201213548288 A US201213548288 A US 201213548288A US 9114528 B2 US9114528 B2 US 9114528B2
Authority
US
United States
Prior art keywords
virtual machine
robot
application
control system
core
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active, expires
Application number
US13/548,288
Other versions
US20130018507A1 (en
Inventor
Michael Haag
Heinrich Munz
Dirk Jacob
Hans-Peter Klüger
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
KUKA Deutschland GmbH
Original Assignee
KUKA Roboter GmbH
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by KUKA Roboter GmbH filed Critical KUKA Roboter GmbH
Assigned to KUKA ROBOTER GMBH reassignment KUKA ROBOTER GMBH ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: KLUGER, HANS-PETER, HAAG, MICHAEL, MUNZ, HEINRICH, JACOB, DIRK
Publication of US20130018507A1 publication Critical patent/US20130018507A1/en
Application granted granted Critical
Publication of US9114528B2 publication Critical patent/US9114528B2/en
Active legal-status Critical Current
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B25—HAND TOOLS; PORTABLE POWER-DRIVEN TOOLS; MANIPULATORS
    • B25J—MANIPULATORS; CHAMBERS PROVIDED WITH MANIPULATION DEVICES
    • B25J9/00—Programme-controlled manipulators
    • B25J9/16—Programme controls
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B25—HAND TOOLS; PORTABLE POWER-DRIVEN TOOLS; MANIPULATORS
    • B25J—MANIPULATORS; CHAMBERS PROVIDED WITH MANIPULATION DEVICES
    • B25J9/00—Programme-controlled manipulators
    • B25J9/16—Programme controls
    • B25J9/1602—Programme controls characterised by the control system, structure, architecture
    • B25J9/161—Hardware, e.g. neural networks, fuzzy logic, interfaces, processor
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B19/00—Programme-control systems
    • G05B19/02—Programme-control systems electric
    • G05B19/04—Programme control other than numerical control, i.e. in sequence controllers or logic controllers
    • G05B19/042—Programme control other than numerical control, i.e. in sequence controllers or logic controllers using digital processors
    • G05B19/0421—Multiprocessor system
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/40—Transformation of program code
    • G06F8/54—Link editing before load time
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00—Program-control systems
    • G05B2219/20—Pc systems
    • G05B2219/22—Pc multi processor system
    • G05B2219/2205—Multicore
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00—Program-control systems
    • G05B2219/20—Pc systems
    • G05B2219/22—Pc multi processor system
    • G05B2219/2208—Each processor controls a different function of the machine
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00—Program-control systems
    • G05B2219/20—Pc systems
    • G05B2219/22—Pc multi processor system
    • G05B2219/2227—Common memory as well as local memory
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00—Program-control systems
    • G05B2219/30—Nc systems
    • G05B2219/34—Director, elements to supervisory
    • G05B2219/34069—Shared memory
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/02—Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]

Definitions

  • the present invention concerns a control system for a robot with multi-core architecture, comprising virtual machines, as well as a method for controlling robots having such a control system.
  • robots are controlled through motion control, while process applications, for example, welding guns, have their own process controls, different from this concept. These separate controls communicate via field busses.
  • the motion control reports to the process control that the robot has approached a welding spot, whereupon the process control closes the welding gun and loads it with welding current.
  • the process control reports this to the motion control, which then approaches the next welding spot.
  • the present invention has the objective of improving a robot control.
  • An invention-based control has the objective of controlling a robot or an arrangement of several robots.
  • control also a regulation, i.e., presetting of control factors in consideration of repatriated actual values.
  • the control system comprises a multi-core architecture with at least two, in particular at least three, preferably four, six or more, preferably double integer computing engines.
  • the multi-core architecture is formed by a microprocessor on a chip with several computing engines, wherein in this context the term computing engine refers to an at least basically complete central processing unit (CPU), which comprises its own arithmetic logic unit, its own register, its own instruction decoder and/or its own floating point unit.
  • CPU central processing unit
  • a multi-core architecture in the sense of the present invention can be formed also by multi-threaded-CPUs with several program counters and register sets, acting as several cores. It is even possible to combine them, for example, combining a dual core processor with two threads per core, as, for example the IBM Power5 processor, or an eight core processor with four threads per core, as for example, the Sun UltraSPARC T1 processor.
  • At least one, preferably two or several virtual machines are represented by means of the multi-core architecture.
  • One virtual machine in the sense of the present invention involves especially an instance or computing environment, which is preferably software or programmatically implemented, and which preferably acts as an independent, physical computer, which means that several virtual machines can run simultaneously on the same physical computer.
  • a virtual machine can comprise or be its own operating system and/or its own runtime environment, under or in which programs can be implemented.
  • a process control which controls one, several or all process applications of one robot or several robots of a robot arrangement, is implemented by a first virtual machine, which comprises one or several computing engines of the multi-core architecture.
  • a motion control which controls one, several or all drivers of this robot or this robot arrangement, is implemented by a second virtual machine, which comprises one or several further computing engines of the multi-core architecture.
  • the process control is integrated as a virtual machine directly into the robot control of at least one particular computing engine of a multi-core architecture, in which the motion control is implemented as the other virtual machine of the multi-core architecture.
  • This has the advantage that the above-mentioned jitter can be reduced or prevented, especially when in one preferred embodiment these two virtual machines are synchronized.
  • it is possible to reduce hardware, installation space, operating energy, waste heat and/or wiring costs and/or to share resources, such as special input and/or output facilities, memory devices, communication networks, interfaces and the like.
  • an invention-based implementation of a process control as further virtual machine can increase mutual, process-oriented robot programming, mutual user and/or policy management, diagnosis and/or recording for motion and process control, and/or allow for an implementation of an integrated safety monitoring system of robot motions and process applications and/or increase the system availability.
  • both virtual machines have a shared memory, it is possible to improve archiving and/or Online-quality control, because the required data is available in one location and therefore simultaneously available.
  • this allows the robot manufacturer to provide a container with definite interfaces, in which the process manufacturer can easily integrate his process control.
  • this makes it possible to simplify modifications of a process control.
  • this reduces the risk that a slow or defective process control impedes or sabotages the motion control.
  • it is also possible to perform a restart of the process control without restarting the motion control.
  • different runtime environments or operating systems are realized, as, for example, VxWorks (SMP), Windows CE or VxWin, QNX, On Time RTOS32 or EUROS.
  • a virtual machine which has been provided for a particular task, especially a process control, involves in particular a virtual machine that is equipped to perform this particular task, possibly after it has been implemented in a container.
  • a third virtual machine can be provided for user communication, data processing and/or data administration.
  • the first and/or second virtual machine comprise real-time operating systems (RTOS) for process or motion control
  • the preferred embodiment of the third virtual machine does not real-time capabilities (N-RTOS), but can, for example, perform a Windows operating system.
  • RTOS real-time operating systems
  • N-RTOS real-time capabilities
  • user communication involves especially data input by a user, for example, by means of a keyboard or graphic based, especially through mouse or touch screen, and/or data input, especially on a monitor
  • data administration involves especially organizing and/or saving data
  • data processing involves a logical and/or arithmetic combination of data.
  • the third virtual machine can be used especially for programming, performing and/or modifying the motion and/or process control.
  • each computing engine is used only by one virtual machine.
  • two or more virtual machines can jointly access one or several computing engines.
  • the second virtual machine has two computing engines, the first virtual machine has one computing engine.
  • at least two, preferably all computing engines are identical, i.e., the multi-core architecture is symmetrical, so that the virtual machines can be distributed selectively to the different cores.
  • the multi-core architecture is symmetrical, so that the virtual machines can be distributed selectively to the different cores.
  • two or more, in particular all virtual machines of the multi-core architecture have a shared memory, respectively.
  • This shared memory can comprise, respectively, the complete physical memory of the multi-core architecture or only a particular section of it. This allows for quick, reliable data exchange.
  • a virtual machine can access the shared memory of two additional virtual machines or an individual section of it.
  • all virtual machines can be provided with an absolute system time clock.
  • provision can be made that in particular only two virtual machines have access to the shared memory instead of all virtual machines, especially in order to prevent data corruption or an impairment of real-time capability.
  • the motion control is able to store in the shared memory images of a bus by means of which it communicates with the drivers and/or sensors, so that the process control can preferably have access to them, especially to engine and joint positions or the values of other sensors, for example, distance sensors, only in reading mode.
  • the process control can set flags in the shared memory and in this way inform the motion control about the process status and preferably command the processing of further motion steps.
  • one or several virtual machines can control, especially by means of pointers and/or spin locks, the access to the shared memory.
  • a data range of a virtual I/O-driver can be displayed in a shared memory.
  • a bus for communication of one virtual machine with one or several further virtual machines can be provided.
  • a bus involves especially generalized a physical or virtual network and/or network protocol, in particular a field bus and preferably a real-time-capable bus, especially an EtherCAT.
  • the virtual machine is able to communicate via this or any additional bus with robot drivers.
  • the virtual machine is able to communicate via this or any additional bus with process application peripheries, input and/or output facilities for user communication, memory devices and/or interfaces. It is therefore possible that different busses are involved, or two or several communications can take place via the same bus.
  • the motion control can communicate via a real-time-capable field bus with the drivers of a robot or a robot arrangement.
  • the process control can communicate via this bus also with its periphery and the motion control, thus receiving directly the data of the drivers.
  • the communication between motion control and drivers, on the one hand, and process control and periphery, on the other hand, can also take place via different field busses and the process control can receive data of the drivers from the shared memory by displaying an image of the field busses between motion control and drivers.
  • a safety monitoring system has been provided.
  • this can be provided in a virtual machine in the sense of the present computing environment, i.e., especially in a preferably programmatically defined instance environment of the multi-core architecture.
  • this can involve the second virtual machine.
  • different cores of the second virtual machine can be provided for motion control and for a safety monitoring system, provided the second virtual machine has at least two computing engines.
  • it can be preferred to distribute the redundant, preferably diverse safety monitoring system, to two or more cores and/or two or more virtual machines.
  • the safety monitoring system communicates with the process control via a virtual I/O driver, which has a data range that can be displayed in the shared memory.
  • a safety monitoring system involves especially the professional comparison of actual values of the robots or robot arrangements with permissible limit values, the monitoring of workspaces and/or shelters, entrance ways and the like.
  • a process application in the sense of the present invention can involve a cutting application, especially a cutting application with a solid blade or a cutting application without a solid blade, as, for example, a water jet cutting or laser cutting application.
  • a cutting application can involve also a general machining application, especially a milling and/or sawing application.
  • a periphery of such a cutting application can comprise a robot-controlled cutting or milling head which have drivers and, preferably sensors, for example, for distance or position measurements.
  • a process application can involve a joining application, especially a gluing, welding, screwing, riveting and/or sticking application.
  • a periphery of such a joining application can comprise a robot-controlled glue or rivet gun or welding gun, a robot-controlled screwdriver or grabber, or the like, which have drivers and, preferably, sensors.
  • a process application can involve a surface processing application, especially a coating application, preferably a varnishing and/or polishing application.
  • a periphery of such a surface processing application can comprise a robot-controlled spray gun, a robot-controlled polishing disc, or the like, which have drivers and, preferably, sensors.
  • a process application can involve a transportation application, especially a grabbing application.
  • a grabbing application involves generally a detachable, mechanical, especially a form and/or friction locking, pneumatic and/or (electro) magnetic fixation of a work piece to a robot.
  • a periphery of such a transportation application can comprise a mechanical, (electro) magnetic and/or vacuum gripper.
  • two or more virtual machines have been synchronized.
  • one or several virtual machines can receive synchronization interrupts from a different virtual machine.
  • FIG. 1 a control system of a robot according to an embodiment of the present invention.
  • FIG. 1 shows a control system of a robot with a (jointly displayed) plurality of drivers A, which comprise a multi-core architecture with four separate physical computing engines C 1 . . . C 4 and a physical memory S, with which the computing engines C 1 . . . C 4 , exchange data in customary manner, as indicated by the double arrows.
  • the motion control for the drivers A is implemented in a second virtual machine V 2 , which comprises the computing engine C 1 , C 2 , as well as part of the physical memory S.
  • a safety monitoring system is implemented redundantly on the first and second computing engine C 1 , C 2 of the second virtual machine and monitors the robot and its process applications, for example, a welding process with a welding gun, varnishing process with a spray gun or a grabbing process with a grabber, the actuators and sensors of which, for example, engines, electrodes and dynamometers of the welding gun, valve, pressure and filling level sensors of the spray gun or electromotive and/or—magnetic, hydraulic and/or pneumatic grabber drivers are shown in FIG. 1 jointly as periphery P of the process application.
  • This process application is controlled by a process control. As indicated in FIG. 1 by a dashed line, this process control is implemented in a first virtual machine V 1 , which comprises the third computing engine C 3 , as well as part of the physical memory S, which partially intersects with the part which is also allocated to the second virtual machine. This intersection (shown hatched in FIG. 1 ) forms a shared memory M 1 of the first and second virtual machine V 1 , V 2 .
  • Each of these two virtual machines V 1 , V 2 has different, real-time-capable runtime environments or operating systems. In this way, it is easy for a process manufacturer to integrate his process control in the control system.
  • the fourth computing engine C 4 involves a third virtual machine V 3 with a non-real-time capable Windows operating system implemented especially for user communication, as well as data administration.
  • the third virtual machine V 3 comprises also part of the physical memory S, which partially intersects with the part allocated to the second virtual machine V 2 , partially with the part allocated to the first virtual machine V 1 , and partially with the part allocated to the first and second virtual machine V 1 , V 2 .
  • These intersections form a shared memory M 2 of the second and third virtual machine V 2 , V 3 (shown hatched in FIG. 1 ), a shared memory M 3 of the first and third virtual machine V 1 , V 3 (shown hatched in FIG. 1 ), or a shared memory M 1 ⁇ M 2 ⁇ M 3 for all three virtual machines V 1 . . . V 3 (shown cross-hatched in FIG. 1 ).
  • FIG. 1 shows hatched a virtual bus B by means of which the first virtual machine V 1 is communicating for process control with the periphery P of the process application, the second virtual machine V 2 is communicating for motion control with the drivers A of the robot, and the third virtual machine V 3 is communicating with an input and output facility I/O, for example, a keyboard, a monitor and/or a hand-held controller, as well as the three virtual machines V 1 . . . V 3 are communicating among one another, i.e., are exchanging uni or bidirectional data.
  • I/O input and output facility
  • busses for communication between the first virtual machine V 1 and the periphery P, between the second virtual machine V 2 and the drivers A, between the third virtual machine V 3 and the input and output facility I/O, between the first and the second virtual machine V 1 , V 2 , between the first and the third virtual machine V 1 , V 3 and/or between the second and the third virtual machine V 2 , V 3 .
  • one or several busses are designed as EtherCAT-Bus.
  • the three virtual busses communicate via the virtual bus or busses B and, on the other hand, via the shared memory M 1 . . . M 3 .
  • the process control communicates with the Windows application for user communication via the internal, multi-user-capable virtual TCP/UDP/IP-network B.
  • a process control surface can be displayed on the monitor and/or the hand-held controller.
  • SMP runtime environment VxWorks
  • the shared memory M 1 is available as communication interface for motion control.
  • the respective functionality of this memory is preset by the process control manufacturer and the process control can access the memory in reading and writing mode. Since the process control runs on a separate computing engine C 3 , the process control cannot make any direct invocations into the motion control or the Windows application. Instead, all desired functionalities which should trigger actions in the motion control have to be displayed on the shared memory and respectively programmed on the side of the motion control. When the function has been performed, the motion control can respond by returning a status or error message. It is recommended not to wait for this response actively circling on the spot but to analyze the response in the cycle of the process control.
  • the following mechanisms are available for the process control: it is possible to display cyclically data images of the field busses between drivers A and the second virtual machine V 2 in the address space of the process control in the shared memory M 1 .
  • the administration of access to these data images takes place via this shared memory M 1 .
  • pointers and spin locks for locking the accesses can be filed.
  • CoE CAN application layer over EtherCAT
  • a virtual I/O driver For communication with the motion control and/or the safety monitoring system, a virtual I/O driver is available, the data range of which is also displayed in the shared memory. Administration also takes place via pointers and spin locks for locking.
  • the process control can access also the global administration data of the motion control, such as the global EtherCAT system time, and is thus able to synchronize via the absolute system time precisely with the motion control.
  • the global administration data of the motion control such as the global EtherCAT system time

Landscapes

  • Engineering & Computer Science (AREA)
  • Automation & Control Theory (AREA)
  • Physics & Mathematics (AREA)
  • Mechanical Engineering (AREA)
  • Software Systems (AREA)
  • Robotics (AREA)
  • General Physics & Mathematics (AREA)
  • Evolutionary Computation (AREA)
  • Fuzzy Systems (AREA)
  • Mathematical Physics (AREA)
  • Artificial Intelligence (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Numerical Control (AREA)

Abstract

An invention-based control system for at least one robot comprises a, especially symmetric, multi-core architecture with a first virtual machine (V1) with at least one computing engine (C3), which has been provided for controlling at least one process application (P) of this robot.

Description

The present invention concerns a control system for a robot with multi-core architecture, comprising virtual machines, as well as a method for controlling robots having such a control system.
Based on our company-internal experience robots are controlled through motion control, while process applications, for example, welding guns, have their own process controls, different from this concept. These separate controls communicate via field busses. For example, the motion control reports to the process control that the robot has approached a welding spot, whereupon the process control closes the welding gun and loads it with welding current. When the welding process is finished, the process control reports this to the motion control, which then approaches the next welding spot.
Unfortunately this involves that the time of information transfer varies. This variation can range between a minimum, which is preset by the transmission time of the field bus, and a maximum, which results from adding the cycle times of the one control, the field bus and the other control. These variations, the so-called jitter, affect the repeatability of the robot processes.
The present invention has the objective of improving a robot control.
This objective is achieved through a control comprising the characteristics of Claim 1 or a method involving the characteristics of Claim 8. Advantageous further developments of the invention are included in the sub-claims.
An invention-based control has the objective of controlling a robot or an arrangement of several robots. For a more compact representation we would place under the general term control also a regulation, i.e., presetting of control factors in consideration of repatriated actual values.
The control system comprises a multi-core architecture with at least two, in particular at least three, preferably four, six or more, preferably double integer computing engines. In a preferred embodiment, the multi-core architecture is formed by a microprocessor on a chip with several computing engines, wherein in this context the term computing engine refers to an at least basically complete central processing unit (CPU), which comprises its own arithmetic logic unit, its own register, its own instruction decoder and/or its own floating point unit. Similarly a multi-core architecture in the sense of the present invention can be formed also by multi-threaded-CPUs with several program counters and register sets, acting as several cores. It is even possible to combine them, for example, combining a dual core processor with two threads per core, as, for example the IBM Power5 processor, or an eight core processor with four threads per core, as for example, the Sun UltraSPARC T1 processor.
According to the invention, at least one, preferably two or several virtual machines are represented by means of the multi-core architecture. One virtual machine in the sense of the present invention involves especially an instance or computing environment, which is preferably software or programmatically implemented, and which preferably acts as an independent, physical computer, which means that several virtual machines can run simultaneously on the same physical computer. In particular, a virtual machine can comprise or be its own operating system and/or its own runtime environment, under or in which programs can be implemented. In particular, it is possible to provide within those virtual machines runtime environments which, on their part, act as virtual machines, for example, a Java Virtual Machine or KUKA.PLC ProConOs by the applicant.
According to the invention, a process control, which controls one, several or all process applications of one robot or several robots of a robot arrangement, is implemented by a first virtual machine, which comprises one or several computing engines of the multi-core architecture.
In a preferred embodiment, a motion control, which controls one, several or all drivers of this robot or this robot arrangement, is implemented by a second virtual machine, which comprises one or several further computing engines of the multi-core architecture.
Therefore, the process control is integrated as a virtual machine directly into the robot control of at least one particular computing engine of a multi-core architecture, in which the motion control is implemented as the other virtual machine of the multi-core architecture. This has the advantage that the above-mentioned jitter can be reduced or prevented, especially when in one preferred embodiment these two virtual machines are synchronized. In addition, or alternatively, it is possible to reduce hardware, installation space, operating energy, waste heat and/or wiring costs and/or to share resources, such as special input and/or output facilities, memory devices, communication networks, interfaces and the like. In addition or alternatively, besides motion control, an invention-based implementation of a process control as further virtual machine can increase mutual, process-oriented robot programming, mutual user and/or policy management, diagnosis and/or recording for motion and process control, and/or allow for an implementation of an integrated safety monitoring system of robot motions and process applications and/or increase the system availability. Especially when in a preferred embodiment both virtual machines have a shared memory, it is possible to improve archiving and/or Online-quality control, because the required data is available in one location and therefore simultaneously available.
Advantageously, this allows the robot manufacturer to provide a container with definite interfaces, in which the process manufacturer can easily integrate his process control. In particular, this makes it possible to simplify modifications of a process control. Preferably, this reduces the risk that a slow or defective process control impedes or sabotages the motion control. Advantageously, it is also possible to perform a restart of the process control without restarting the motion control. It is also of advantage that on different virtual machines different runtime environments or operating systems are realized, as, for example, VxWorks (SMP), Windows CE or VxWin, QNX, On Time RTOS32 or EUROS. Correspondingly, a virtual machine, which has been provided for a particular task, especially a process control, involves in particular a virtual machine that is equipped to perform this particular task, possibly after it has been implemented in a container.
Especially when the multi-core architecture comprises an additional computing engine, a third virtual machine can be provided for user communication, data processing and/or data administration. While, preferably, the first and/or second virtual machine comprise real-time operating systems (RTOS) for process or motion control, the preferred embodiment of the third virtual machine does not real-time capabilities (N-RTOS), but can, for example, perform a Windows operating system. In the present case, user communication involves especially data input by a user, for example, by means of a keyboard or graphic based, especially through mouse or touch screen, and/or data input, especially on a monitor, data administration involves especially organizing and/or saving data, data processing involves a logical and/or arithmetic combination of data. Accordingly, the third virtual machine can be used especially for programming, performing and/or modifying the motion and/or process control.
In a preferred embodiment, each computing engine is used only by one virtual machine. In an alternative embodiment, two or more virtual machines can jointly access one or several computing engines. In a preferred development of the invention, the second virtual machine has two computing engines, the first virtual machine has one computing engine. In a preferred embodiment, at least two, preferably all computing engines are identical, i.e., the multi-core architecture is symmetrical, so that the virtual machines can be distributed selectively to the different cores. However, similarly it is also possible to provide an asymmetrical multi-core architecture, which has the advantage that the cores and virtual machines can be specifically adapted to one another.
Preferably, two or more, in particular all virtual machines of the multi-core architecture have a shared memory, respectively. This shared memory (SM) can comprise, respectively, the complete physical memory of the multi-core architecture or only a particular section of it. This allows for quick, reliable data exchange. At the same time, it is possible to provide programmatically a shared memory as an individual section of a physical memory. In a preferred development of the invention, a virtual machine can access the shared memory of two additional virtual machines or an individual section of it. For example, all virtual machines can be provided with an absolute system time clock. In a similar manner, provision can be made that in particular only two virtual machines have access to the shared memory instead of all virtual machines, especially in order to prevent data corruption or an impairment of real-time capability.
In a preferred embodiment, the motion control is able to store in the shared memory images of a bus by means of which it communicates with the drivers and/or sensors, so that the process control can preferably have access to them, especially to engine and joint positions or the values of other sensors, for example, distance sensors, only in reading mode. In particular, the process control can set flags in the shared memory and in this way inform the motion control about the process status and preferably command the processing of further motion steps. In general, one or several virtual machines can control, especially by means of pointers and/or spin locks, the access to the shared memory. In addition or alternatively, a data range of a virtual I/O-driver can be displayed in a shared memory.
In addition or alternatively to this communication via shared memories, a bus for communication of one virtual machine with one or several further virtual machines can be provided. In this context, a bus involves especially generalized a physical or virtual network and/or network protocol, in particular a field bus and preferably a real-time-capable bus, especially an EtherCAT.
The virtual machine is able to communicate via this or any additional bus with robot drivers. In addition or alternatively, the virtual machine is able to communicate via this or any additional bus with process application peripheries, input and/or output facilities for user communication, memory devices and/or interfaces. It is therefore possible that different busses are involved, or two or several communications can take place via the same bus. For example, the motion control can communicate via a real-time-capable field bus with the drivers of a robot or a robot arrangement. In one embodiment, the process control can communicate via this bus also with its periphery and the motion control, thus receiving directly the data of the drivers. Similarly, the communication between motion control and drivers, on the one hand, and process control and periphery, on the other hand, can also take place via different field busses and the process control can receive data of the drivers from the shared memory by displaying an image of the field busses between motion control and drivers.
In a preferred embodiment, a safety monitoring system has been provided. Preferably, this can be provided in a virtual machine in the sense of the present computing environment, i.e., especially in a preferably programmatically defined instance environment of the multi-core architecture. In particular, this can involve the second virtual machine. In a preferred embodiment, different cores of the second virtual machine can be provided for motion control and for a safety monitoring system, provided the second virtual machine has at least two computing engines. Similarly, it can be preferred to distribute the redundant, preferably diverse safety monitoring system, to two or more cores and/or two or more virtual machines. Preferably, the safety monitoring system communicates with the process control via a virtual I/O driver, which has a data range that can be displayed in the shared memory. In this context, a safety monitoring system involves especially the professional comparison of actual values of the robots or robot arrangements with permissible limit values, the monitoring of workspaces and/or shelters, entrance ways and the like.
In particular, a process application in the sense of the present invention can involve a cutting application, especially a cutting application with a solid blade or a cutting application without a solid blade, as, for example, a water jet cutting or laser cutting application. In this context, such a cutting application can involve also a general machining application, especially a milling and/or sawing application. In particular, a periphery of such a cutting application can comprise a robot-controlled cutting or milling head which have drivers and, preferably sensors, for example, for distance or position measurements.
In addition or alternatively, a process application can involve a joining application, especially a gluing, welding, screwing, riveting and/or sticking application. In particular, a periphery of such a joining application can comprise a robot-controlled glue or rivet gun or welding gun, a robot-controlled screwdriver or grabber, or the like, which have drivers and, preferably, sensors.
Moreover, in addition or alternatively, a process application can involve a surface processing application, especially a coating application, preferably a varnishing and/or polishing application. In particular, a periphery of such a surface processing application can comprise a robot-controlled spray gun, a robot-controlled polishing disc, or the like, which have drivers and, preferably, sensors.
Furthermore, in addition or alternatively, a process application can involve a transportation application, especially a grabbing application. In this context, a grabbing application involves generally a detachable, mechanical, especially a form and/or friction locking, pneumatic and/or (electro) magnetic fixation of a work piece to a robot. In particular, a periphery of such a transportation application can comprise a mechanical, (electro) magnetic and/or vacuum gripper.
As mentioned above, in one preferred embodiment, two or more virtual machines have been synchronized. For this purpose, one or several virtual machines can receive synchronization interrupts from a different virtual machine. In addition or alternatively, it is also possible to synchronize via an absolute system timer, with which the virtual machines to be synchronized communicate.
Further advantages and characteristics are included in the sub-claims and the embodiments. To this end, the only figure shows, partly in schematized form, the following:
FIG. 1: a control system of a robot according to an embodiment of the present invention.
FIG. 1 shows a control system of a robot with a (jointly displayed) plurality of drivers A, which comprise a multi-core architecture with four separate physical computing engines C1 . . . C4 and a physical memory S, with which the computing engines C1 . . . C4, exchange data in customary manner, as indicated by the double arrows.
As indicated in FIG. 1 by a dashed line, the motion control for the drivers A is implemented in a second virtual machine V2, which comprises the computing engine C1, C2, as well as part of the physical memory S. A safety monitoring system is implemented redundantly on the first and second computing engine C1, C2 of the second virtual machine and monitors the robot and its process applications, for example, a welding process with a welding gun, varnishing process with a spray gun or a grabbing process with a grabber, the actuators and sensors of which, for example, engines, electrodes and dynamometers of the welding gun, valve, pressure and filling level sensors of the spray gun or electromotive and/or—magnetic, hydraulic and/or pneumatic grabber drivers are shown in FIG. 1 jointly as periphery P of the process application.
This process application is controlled by a process control. As indicated in FIG. 1 by a dashed line, this process control is implemented in a first virtual machine V1, which comprises the third computing engine C3, as well as part of the physical memory S, which partially intersects with the part which is also allocated to the second virtual machine. This intersection (shown hatched in FIG. 1) forms a shared memory M1 of the first and second virtual machine V1, V2.
Each of these two virtual machines V1, V2 has different, real-time-capable runtime environments or operating systems. In this way, it is easy for a process manufacturer to integrate his process control in the control system.
As indicated in FIG. 1 by a dashed-dotted line, the fourth computing engine C4 involves a third virtual machine V3 with a non-real-time capable Windows operating system implemented especially for user communication, as well as data administration. The third virtual machine V3 comprises also part of the physical memory S, which partially intersects with the part allocated to the second virtual machine V2, partially with the part allocated to the first virtual machine V1, and partially with the part allocated to the first and second virtual machine V1, V2. These intersections form a shared memory M2 of the second and third virtual machine V2, V3 (shown hatched in FIG. 1), a shared memory M3 of the first and third virtual machine V1, V3 (shown hatched in FIG. 1), or a shared memory M1∩M2∩M3 for all three virtual machines V1 . . . V3 (shown cross-hatched in FIG. 1).
FIG. 1 shows hatched a virtual bus B by means of which the first virtual machine V1 is communicating for process control with the periphery P of the process application, the second virtual machine V2 is communicating for motion control with the drivers A of the robot, and the third virtual machine V3 is communicating with an input and output facility I/O, for example, a keyboard, a monitor and/or a hand-held controller, as well as the three virtual machines V1 . . . V3 are communicating among one another, i.e., are exchanging uni or bidirectional data. Similarly, it is also possible to provide separate busses for communication between the first virtual machine V1 and the periphery P, between the second virtual machine V2 and the drivers A, between the third virtual machine V3 and the input and output facility I/O, between the first and the second virtual machine V1, V2, between the first and the third virtual machine V1, V3 and/or between the second and the third virtual machine V2, V3. Preferably, one or several busses are designed as EtherCAT-Bus.
On the one hand, the three virtual busses communicate via the virtual bus or busses B and, on the other hand, via the shared memory M1 . . . M3.
For example, the process control communicates with the Windows application for user communication via the internal, multi-user-capable virtual TCP/UDP/IP-network B. For example, in this way a process control surface can be displayed on the monitor and/or the hand-held controller. Additionally, it is possible by means of routing via the second virtual machine V2 to communicate by means of the runtime environment VxWorks (SMP) with an engineering system for the process control.
The shared memory M1 is available as communication interface for motion control. The respective functionality of this memory is preset by the process control manufacturer and the process control can access the memory in reading and writing mode. Since the process control runs on a separate computing engine C3, the process control cannot make any direct invocations into the motion control or the Windows application. Instead, all desired functionalities which should trigger actions in the motion control have to be displayed on the shared memory and respectively programmed on the side of the motion control. When the function has been performed, the motion control can respond by returning a status or error message. It is recommended not to wait for this response actively circling on the spot but to analyze the response in the cycle of the process control.
For communication with the drivers A, including their sensors, for example, angular encoders or the like, the following mechanisms are available for the process control: it is possible to display cyclically data images of the field busses between drivers A and the second virtual machine V2 in the address space of the process control in the shared memory M1. The administration of access to these data images takes place via this shared memory M1. Here pointers and spin locks for locking the accesses can be filed. In addition or alternatively, it is possible to communicate acyclic via the virtual TCP/UDP/IP network B, for example, by means of CoE (CAN application layer over EtherCAT). For this purpose, it is possible to use with EtherCAT the remote API.
For communication with the motion control and/or the safety monitoring system, a virtual I/O driver is available, the data range of which is also displayed in the shared memory. Administration also takes place via pointers and spin locks for locking.
By means of the shared memory, the process control can access also the global administration data of the motion control, such as the global EtherCAT system time, and is thus able to synchronize via the absolute system time precisely with the motion control.
REFERENCE LIST
  • A drivers of the robots
  • B virtual bus
  • C1 . . . C4 computing engine
  • I/O input and output facility (keyboard, monitor, hand-held controller)
  • M1 . . . M3 shared memory
  • P periphery
  • S physical memory
  • V1 . . . V3 virtual machine

Claims (11)

The invention claimed is:
1. A control system for at least one robot, with a, especially symmetrical, multi-core-architecture formed by a microprocessor on a chip with several computing engines said multi-core-architecture representing a first virtual machine, wherein said first virtual machine comprises at least one of said computing engines, and wherein the first virtual machine has been provided for controlling at least one process application of a robot,
wherein the multi-core architecture comprises a second virtual machine with at least one further computing engine, and the second virtual machine has been provided for motion control with at least one drive of the robot.
2. The control system according to claim 1, wherein the multi-core architecture comprises a third virtual machine with at least one further computing engine, which has been provided for user communication, data processing and/or data administration.
3. The control system according to claim 2, wherein at least two of the virtual machines have a shared memory.
4. The control system according to claim 1, further comprising:
at least one bus for communication of one virtual machine with at least one further virtual machine, at least one drive, at least one robot, at least one periphery, at least one process application, at least one input and output facility for user communication, at least one interface and/or at least one memory.
5. Control system according to claim 1, further comprising a safety monitoring system.
6. Control system according to claim 1, characterized in that a process application comprises a cutting application, especially a cutting and joining application, especially a gluing, welding, screwing, riveting and/or sticking application, a surface processing application, especially a coating, preferably varnishing, and/or polishing application, and/or a transporting application, especially a grabbing application.
7. A method for controlling at least one robot, comprising:
controlling at least one process application of the at least one robot with a first virtual machine of a control system,
wherein the control system is connected to a plurality of drives of at least one robot, and the control system comprises a shared memory and a microprocessor on a chip that includes a plurality of processing cores configured in a plurality of computing engines,
wherein the first virtual machine is implemented in a first computing engine of the plurality of computing engines and configured to control at least one process application of the robot, and
wherein a second virtual machine is configured for motion control with at least one drive of the plurality of drives of the robot.
8. The method of claim 7, wherein the control system further comprises at least one further virtual machine, at least one periphery, at least one additional process application, at least one input and/or output facility for user communication and/or at least one shared memory for communication and/or via a bus.
9. The method of claim 7, wherein the first virtual machine and the second virtual machine are synchronized.
10. The method of claim 7, wherein a program to be processed from the second virtual machine for controlling the at least one drive of the robot and a program to be processed from the first virtual machine for controlling the at least one process application of the robot are prepared mutually or separately in different runtime environments.
11. A control system for at least one robot, with a, especially symmetrical, multi-core-architecture formed by a microprocessor on a chip with several computing engines said multi-core-architecture representing a first virtual machine, wherein each of said computing engines is used only by one virtual machine, and wherein the first virtual machine has been provided for controlling at least one process application of a robot.
US13/548,288 2011-07-13 2012-07-13 Control system of a robot Active 2032-09-28 US9114528B2 (en)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
DE102011107169.9 2011-07-13
DE102011107169A DE102011107169A1 (en) 2011-07-13 2011-07-13 Control of a robot
DE102011107169 2011-07-13

Publications (2)

Publication Number Publication Date
US20130018507A1 US20130018507A1 (en) 2013-01-17
US9114528B2 true US9114528B2 (en) 2015-08-25

Family

ID=46419855

Family Applications (1)

Application Number Title Priority Date Filing Date
US13/548,288 Active 2032-09-28 US9114528B2 (en) 2011-07-13 2012-07-13 Control system of a robot

Country Status (5)

Country Link
US (1) US9114528B2 (en)
EP (1) EP2546029A3 (en)
KR (1) KR20130009658A (en)
CN (1) CN102880064A (en)
DE (1) DE102011107169A1 (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210197374A1 (en) * 2019-12-30 2021-07-01 X Development Llc Composability framework for robotic control system
US12045038B2 (en) 2019-07-03 2024-07-23 Beckhoff Automation Gmbh Runtime server for simultaneous execution of a plurality of runtime systems of an automation system

Families Citing this family (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9925628B2 (en) * 2012-03-29 2018-03-27 The Boeing Company Method for installing fasteners with electromagnetic effect protection
DE102013100466A1 (en) * 2013-01-17 2014-07-17 Netstal-Maschinen Ag Microprocessor-controlled control device for an injection molding plant
CN104903800A (en) * 2013-01-17 2015-09-09 Abb技术有限公司 Motion controller and robot control system using the same
US20150121374A1 (en) * 2013-10-30 2015-04-30 Alistair Black Application Processing Systems and Methods
KR102235166B1 (en) * 2015-09-21 2021-04-02 주식회사 레인보우로보틱스 A realtime robot system, an appratus for controlling a robot system, and a method for controlling a robot system
US10894318B2 (en) * 2016-02-23 2021-01-19 Abb Schweiz Ag Robot controller system and method therefor
WO2018074590A1 (en) * 2016-10-21 2018-04-26 株式会社東芝 Controller
US11554461B1 (en) 2018-02-13 2023-01-17 Omax Corporation Articulating apparatus of a waterjet system and related technology
CN108614460B (en) * 2018-06-20 2020-11-06 东莞市李群自动化技术有限公司 Distributed multi-node control system and method
KR102258667B1 (en) * 2018-06-22 2021-06-01 소프트 서보 시스템즈 가부시키가이샤 Motion control program, motion control method and motion control device
WO2020047780A1 (en) * 2018-09-05 2020-03-12 西门子股份公司 Redundant hot standby control system and control device, redundant hot standby method and computer-readable storage medium
KR20200129892A (en) 2019-05-10 2020-11-18 (주)새온 Processing method for educational robot having multi processor
EP3739396A1 (en) * 2019-05-15 2020-11-18 Siemens Aktiengesellschaft Motion control system of a manipulator comprising a first and a second processor
CN111381937A (en) * 2020-04-02 2020-07-07 中国电子科技网络信息安全有限公司 Experimental scene snapshot generating system and method based on time base line
CN112894827B (en) * 2021-02-25 2022-09-02 中国科学院长春光学精密机械与物理研究所 Method, system and device for controlling motion of mechanical arm and readable storage medium
US12210329B2 (en) * 2021-06-16 2025-01-28 Fisher-Rosemount Systems, Inc. Systems and methods for dynamically maintained redundancy and load balancing in software defined control systems for industrial process plants

Citations (39)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020055910A1 (en) * 1998-09-10 2002-05-09 David John Durbin Program component distribution
US20040128670A1 (en) * 2002-12-27 2004-07-01 Robinson Scott H. Dynamic service registry for virtual machines
US20040181782A1 (en) * 2003-03-13 2004-09-16 Piotr Findeisen System and method for optimizing memory usage by locating lingering objects
US20050160151A1 (en) * 2003-12-17 2005-07-21 International Business Machines Corporation Method and system for machine memory power and availability management in a processing system supporting multiple virtual machines
US6973560B1 (en) * 1999-07-16 2005-12-06 Lamarck, Inc. Fault tolerant and combinatorial software environment system, method and medium
DE102006012042A1 (en) 2006-03-16 2007-09-20 Kuka Roboter Gmbh Control device e.g. personal computer, for e.g. joint robot, has two channels for processing independent codes with mutual safety monitoring, and main storage provided for accessing two processor cores of multi-processor core
US20070260831A1 (en) * 2006-05-08 2007-11-08 Microsoft Corporation Converting physical machines to virtual machines
US20080028410A1 (en) * 2006-07-26 2008-01-31 Ludmila Cherkasova Systems and methods for flexibly controlling resource usage by a driver domain on behalf of a virtual machine
US20080059769A1 (en) * 2006-08-30 2008-03-06 James Walter Rymarczyk Multiple-core processor supporting multiple instruction set architectures
US7344122B2 (en) * 2004-03-01 2008-03-18 Gasaway Mark S Joint connection and applications
DE102006040416A1 (en) 2006-08-29 2008-03-20 Siemens Ag Device for controlling and / or regulating a machine
US20080092137A1 (en) * 2004-08-12 2008-04-17 Anderson Gary D Method and system for managing peripheral connection wakeup in a processing system supporting multiple virtual machines
US20080141220A1 (en) 2004-05-12 2008-06-12 Korea Institute Of Industrial Technology Robot Control Software Framework in Open Distributed Process Architecture
US7409487B1 (en) * 2003-06-30 2008-08-05 Vmware, Inc. Virtualization system for computers that use address space indentifiers
CN101403983A (en) 2008-11-25 2009-04-08 北京航空航天大学 Resource monitoring method and system for multi-core processor based on virtual machine
US20090133042A1 (en) * 2004-08-20 2009-05-21 Microsoft Corporation Efficient linking and loading for late binding and platform retargeting
US20090132057A1 (en) 2007-11-20 2009-05-21 Abb Research Ltd. Control system for controlling the movements of a plurality of mechanical units
US20090165134A1 (en) * 2007-12-21 2009-06-25 Searete Llc, A Limited Liability Corporation Of The State Of Delaware Look ahead of links/alter links
US20090182979A1 (en) * 2008-01-11 2009-07-16 International Business Machines Corporation Computer Configuration Virtual Topology Discovery and Instruction Therefore
CN101488098A (en) 2009-02-13 2009-07-22 华中科技大学 Multi-core computing resource management system based on virtual computing technology
US20100118884A1 (en) * 2005-04-05 2010-05-13 Ariel Hendel Method for Resolving Mutex Contention in a Network System
DE102008058518A1 (en) 2008-11-21 2010-05-27 Johnson Controls Gmbh Connecting means between a handle and an unlocking means of a vehicle seat
US20100161929A1 (en) * 2008-12-18 2010-06-24 Lsi Corporation Flexible Memory Appliance and Methods for Using Such
US20100205602A1 (en) * 2004-12-16 2010-08-12 Vmware, Inc. Mechanism for Scheduling Execution of Threads for Fair Resource Allocation in a Multi-Threaded and/or Multi-Core Processing System
US7783838B1 (en) * 2004-02-06 2010-08-24 Vmware, Inc. Maintaining coherency of derived data in a computer system
CN101911019A (en) 2008-01-18 2010-12-08 库卡罗伯特有限公司 Computer system, control apparatus for a machine, in particular for an industrial robot, and industrial robot
US20110022773A1 (en) * 2009-07-27 2011-01-27 International Business Machines Corporation Fine Grained Cache Allocation
US20110061043A1 (en) * 2005-01-28 2011-03-10 Samuel Rydh Devices, Methods And Computer Program Products For Reverse Execution Of A Simulation
US7945908B1 (en) 2006-03-31 2011-05-17 Vmware, Inc. Method and system for improving the accuracy of timing and process accounting within virtual machines
US20110126203A1 (en) * 2009-11-25 2011-05-26 Microsoft Corporation Efficient Input/Output-Aware Multi-Processor Virtual Machine Scheduling
US20110145510A1 (en) * 2009-12-14 2011-06-16 International Business Machines Corporation Reducing interprocessor communications pursuant to updating of a storage key
EP2341405A2 (en) 2009-12-30 2011-07-06 Robert Bosch GmbH Method for operating a machine
US8037210B2 (en) * 2008-11-20 2011-10-11 Lenovo (Beijing) Limited Computer and method for directly accessing computer hardware by virtual system
US20110320825A1 (en) * 2010-06-24 2011-12-29 International Business Machines Corporation Function virtualization facility for function query of a processor
US20120011500A1 (en) * 2010-07-09 2012-01-12 Paolo Faraboschi Managing a memory segment using a memory virtual appliance
US20130067135A1 (en) * 2008-06-11 2013-03-14 Vmware, Inc. System and method for improving memory locality of virtual machines
US8468356B2 (en) * 2008-06-30 2013-06-18 Intel Corporation Software copy protection via protected execution of applications
US20130215754A1 (en) * 2010-05-03 2013-08-22 Sunay Tripathi Servers, Switches, and Systems with Switching Module Implementing a Distributed Network Operating System
US8547868B2 (en) * 2007-06-29 2013-10-01 Intel Corporation Cross-layer approach to virtualized overlay on ad hoc networks

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE102006052757B4 (en) * 2006-11-08 2014-10-09 Siemens Aktiengesellschaft Method for operating an automation device with a processing unit having a plurality of processing cores

Patent Citations (40)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020055910A1 (en) * 1998-09-10 2002-05-09 David John Durbin Program component distribution
US6973560B1 (en) * 1999-07-16 2005-12-06 Lamarck, Inc. Fault tolerant and combinatorial software environment system, method and medium
US20040128670A1 (en) * 2002-12-27 2004-07-01 Robinson Scott H. Dynamic service registry for virtual machines
US7962545B2 (en) * 2002-12-27 2011-06-14 Intel Corporation Dynamic service registry for virtual machines
US20040181782A1 (en) * 2003-03-13 2004-09-16 Piotr Findeisen System and method for optimizing memory usage by locating lingering objects
US7409487B1 (en) * 2003-06-30 2008-08-05 Vmware, Inc. Virtualization system for computers that use address space indentifiers
US20050160151A1 (en) * 2003-12-17 2005-07-21 International Business Machines Corporation Method and system for machine memory power and availability management in a processing system supporting multiple virtual machines
US7783838B1 (en) * 2004-02-06 2010-08-24 Vmware, Inc. Maintaining coherency of derived data in a computer system
US7344122B2 (en) * 2004-03-01 2008-03-18 Gasaway Mark S Joint connection and applications
US20080141220A1 (en) 2004-05-12 2008-06-12 Korea Institute Of Industrial Technology Robot Control Software Framework in Open Distributed Process Architecture
US20080092137A1 (en) * 2004-08-12 2008-04-17 Anderson Gary D Method and system for managing peripheral connection wakeup in a processing system supporting multiple virtual machines
US20090133042A1 (en) * 2004-08-20 2009-05-21 Microsoft Corporation Efficient linking and loading for late binding and platform retargeting
US20100205602A1 (en) * 2004-12-16 2010-08-12 Vmware, Inc. Mechanism for Scheduling Execution of Threads for Fair Resource Allocation in a Multi-Threaded and/or Multi-Core Processing System
US20110061043A1 (en) * 2005-01-28 2011-03-10 Samuel Rydh Devices, Methods And Computer Program Products For Reverse Execution Of A Simulation
US20100118884A1 (en) * 2005-04-05 2010-05-13 Ariel Hendel Method for Resolving Mutex Contention in a Network System
DE102006012042A1 (en) 2006-03-16 2007-09-20 Kuka Roboter Gmbh Control device e.g. personal computer, for e.g. joint robot, has two channels for processing independent codes with mutual safety monitoring, and main storage provided for accessing two processor cores of multi-processor core
US7945908B1 (en) 2006-03-31 2011-05-17 Vmware, Inc. Method and system for improving the accuracy of timing and process accounting within virtual machines
US20070260831A1 (en) * 2006-05-08 2007-11-08 Microsoft Corporation Converting physical machines to virtual machines
US20080028410A1 (en) * 2006-07-26 2008-01-31 Ludmila Cherkasova Systems and methods for flexibly controlling resource usage by a driver domain on behalf of a virtual machine
DE102006040416A1 (en) 2006-08-29 2008-03-20 Siemens Ag Device for controlling and / or regulating a machine
US20080059769A1 (en) * 2006-08-30 2008-03-06 James Walter Rymarczyk Multiple-core processor supporting multiple instruction set architectures
US8547868B2 (en) * 2007-06-29 2013-10-01 Intel Corporation Cross-layer approach to virtualized overlay on ad hoc networks
US20090132057A1 (en) 2007-11-20 2009-05-21 Abb Research Ltd. Control system for controlling the movements of a plurality of mechanical units
US20090165134A1 (en) * 2007-12-21 2009-06-25 Searete Llc, A Limited Liability Corporation Of The State Of Delaware Look ahead of links/alter links
US20090182979A1 (en) * 2008-01-11 2009-07-16 International Business Machines Corporation Computer Configuration Virtual Topology Discovery and Instruction Therefore
CN101911019A (en) 2008-01-18 2010-12-08 库卡罗伯特有限公司 Computer system, control apparatus for a machine, in particular for an industrial robot, and industrial robot
US20130067135A1 (en) * 2008-06-11 2013-03-14 Vmware, Inc. System and method for improving memory locality of virtual machines
US8468356B2 (en) * 2008-06-30 2013-06-18 Intel Corporation Software copy protection via protected execution of applications
US8037210B2 (en) * 2008-11-20 2011-10-11 Lenovo (Beijing) Limited Computer and method for directly accessing computer hardware by virtual system
DE102008058518A1 (en) 2008-11-21 2010-05-27 Johnson Controls Gmbh Connecting means between a handle and an unlocking means of a vehicle seat
CN101403983A (en) 2008-11-25 2009-04-08 北京航空航天大学 Resource monitoring method and system for multi-core processor based on virtual machine
US20100161929A1 (en) * 2008-12-18 2010-06-24 Lsi Corporation Flexible Memory Appliance and Methods for Using Such
CN101488098A (en) 2009-02-13 2009-07-22 华中科技大学 Multi-core computing resource management system based on virtual computing technology
US20110022773A1 (en) * 2009-07-27 2011-01-27 International Business Machines Corporation Fine Grained Cache Allocation
US20110126203A1 (en) * 2009-11-25 2011-05-26 Microsoft Corporation Efficient Input/Output-Aware Multi-Processor Virtual Machine Scheduling
US20110145510A1 (en) * 2009-12-14 2011-06-16 International Business Machines Corporation Reducing interprocessor communications pursuant to updating of a storage key
EP2341405A2 (en) 2009-12-30 2011-07-06 Robert Bosch GmbH Method for operating a machine
US20130215754A1 (en) * 2010-05-03 2013-08-22 Sunay Tripathi Servers, Switches, and Systems with Switching Module Implementing a Distributed Network Operating System
US20110320825A1 (en) * 2010-06-24 2011-12-29 International Business Machines Corporation Function virtualization facility for function query of a processor
US20120011500A1 (en) * 2010-07-09 2012-01-12 Paolo Faraboschi Managing a memory segment using a memory virtual appliance

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
Chinese Patent Office; Office Action in Chinese Patent Application No. 201210244542.4 dated Apr. 17, 2014; 12 pages.
Chinese Patent Office; Search Report in Chinese Patent Application No. 201210244542.4 dated Apr. 5, 2014; 2 pages.
German Patent Office; Search Report in German Patent Application No. 10 2011 107 169.9 dated Sep. 30, 2013; 8 pages.
Wong et al.; Publication entitled "Implementation Of Asymmetric Multiprocessing Framework in Humanoid Robot" dated Dec. 31, 2010; 6 pages.
Zhang, J.; Chen, K; Zuo, B.; Ma, R,; Dong, Y.; Guan, H.: "Performance Analysis Towards a KVM-Based Embedded Real-Time Virtualization Architecture", in: Proceedings of the 5th IEEE International Conference on Computer Sciences and Convergence Information, Nov. 30, 2010-Dec. 2, 2010, S. 421-426.

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US12045038B2 (en) 2019-07-03 2024-07-23 Beckhoff Automation Gmbh Runtime server for simultaneous execution of a plurality of runtime systems of an automation system
US20210197374A1 (en) * 2019-12-30 2021-07-01 X Development Llc Composability framework for robotic control system
US11498211B2 (en) * 2019-12-30 2022-11-15 Intrinsic Innovation Llc Composability framework for robotic control system

Also Published As

Publication number Publication date
US20130018507A1 (en) 2013-01-17
EP2546029A3 (en) 2015-10-14
KR20130009658A (en) 2013-01-23
EP2546029A2 (en) 2013-01-16
CN102880064A (en) 2013-01-16
DE102011107169A1 (en) 2013-01-17

Similar Documents

Publication Publication Date Title
US9114528B2 (en) Control system of a robot
US10732601B2 (en) Integrated controller for motion control and motor control
Martinov et al. From classic CNC systems to cloud-based technology and back
US10265848B2 (en) Robotic hybrid system application framework based on multi-core processor architecture
US6807461B2 (en) Coordinated robot control from multiple remote instruction sources
CN105278940B (en) A kind of robot hybrid system application framework based on multi-core processor framework
US9092023B2 (en) Industrial controller using shared memory multicore architecture
US10908577B2 (en) Control device
US20070168082A1 (en) Task-based robot control system for multi-tasking
CN111427310A (en) Industrial robot controller operation system
JP2012066376A (en) Concurrent path planning with one or more humanoid robots
JP2013526419A (en) Method for controlling an automated work cell
JP5149258B2 (en) Robot component management device
US20090132057A1 (en) Control system for controlling the movements of a plurality of mechanical units
US20080234861A1 (en) Control System, Method and Computer Program For Synchronizing Several Robots
Martinov et al. Control of the machine tools with variable kinematics
Mineo et al. Interfacing toolbox for robotic arms with real-time adaptive behavior capabilities
KR100853167B1 (en) Network-based onboard robot control system
Hietanen et al. Proof of concept of a projection-based safety system for human-robot collaborative engine assembly
Zhang et al. A real-time robot control framework using ROS control for 7-DoF light-weight robot
Yu et al. Design of controller system for industrial robot based on RTOS Xenomai
US20200379438A1 (en) Numerical control device
CN104898471A (en) Robot control system and control method
CN102540972B (en) Remote control method supporting multi-point cross-platform communication for numerical control machine
Li et al. Software design of the hybrid robot machine for ITER vacuum vessel assembly and maintenance

Legal Events

Date Code Title Description
AS Assignment

Owner name: KUKA ROBOTER GMBH, GERMANY

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:HAAG, MICHAEL;MUNZ, HEINRICH;JACOB, DIRK;AND OTHERS;SIGNING DATES FROM 20120716 TO 20120731;REEL/FRAME:028802/0482

STCF Information on status: patent grant

Free format text: PATENTED CASE

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 4

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 8

OSZAR »