This application is a national phase application under 35 U.S.C. § 371 of International Patent Application No. PCT/EP2016/001050, filed Jun. 20, 2016 (pending), which claims the benefit of German Patent Application No. DE 10 2015 008 188.8 filed Jun. 25, 2015, the disclosures of which are incorporated by reference herein in their entirety.
The present invention relates to a method for the at least partially automated movement along a predetermined path by a robot, in particular the at least partially automated synchronous movement along a predetermined group of paths with at least two robots, a system and a computer program product for performing the method, as well as a robot setup with the system.
According to in-house practice, robots are moved along predetermined paths, whereby the robots are moved sequentially along predefined sections of the path, which, for example, can be defined by linear, circular or spline movements, whereby the end position of a preceding path section can form the starting position of the subsequent path section. A path section can be specified by the instruction set of a control program, whereby a set pointer successively chooses instruction sets whose corresponding path sections are then traversed as the respectively current path section.
If, particularly after an interruption while traversing the path, the robot is no longer located on the respective current path as selected by the set pointer, for example because after the interruption the robot was manually moved, or the path section was manually changed or the set pointer manually selected a different one of the stored path sections, the robot must (again) be positioned on the (possibly new) current section of the path, before movement along the path or rather the current path section can be performed or continued.
In this case, according to in-house practice, hitherto the robot was moved to the end position of the current path section along a linear path, which is also referred to as a so-called set-coincidence (SAK) movement.
However, if the end position is far away from the current position of the robot, this can cause extended travels offside of the predetermined path, which may not be known in advance and which may be disadvantageous compared with the travels along a predefined, particularly an optimized and/or collision-free planned path.
The function of the present invention is to improve the movement of robots along paths.
This problem is solved by a method for moving along a predetermined path with a robot with features as described herein.
According to one aspect of the present invention, a method for the at least partially automated movement along a predefined, in particular a stored, path with/by a robot includes the following steps:
A system for the at least partially automated movement along a predetermined path with/by a robot according to an aspect of the present invention, in particular a system, in particular a controller, a robot setup with one or more robots according to an aspect of the present invention, is set up by hardware means and/or software means to perform one of the methods described herein and/or features:
The robot or rather at least one of the robots of the robot setup has in an exemplary embodiment at least three, particularly at least six, particularly actuable or motor-actuated joints or axes, particularly swivel joints or rotary axes. In an exemplary embodiment, the robot has a (robot) arm with at least six axes and/or one or more active or actuable and/or passive or rather driveless additional axes to move a robot base relative to the environment.
In an exemplary embodiment, a position of a robot comprises or describes a particular three-dimensional position and/or orientation of a robot-fixed reference, particularly its tool center points, and/or, particularly with redundant robots or singular poses, a unique pose, and/or an axis position or joint position or joint coordinate of one or several or all axes of the robot, particularly one or several or all axes of the arm of the robot and/or additional axes of the robot, in which a base of the arm, particularly actuable or actuated, particularly by motor, is movable. The position can thus be similarly specified in the (Cartesian) workspace or in the joint coordinate space or axis coordinate space of the robot.
Accordingly, components of the particularly multidimensional, particularly at least six-dimensional, position, are in the present case generally referred to as coordinates of the robot; they can comprise, or be, particularly joint coordinates, particularly joint angles, position coordinates, orientation angles such as particularly EULER or CARDAN angles, Denavit-Hartenberg parameters, quaternion fields or the like.
In an exemplary embodiment, one path or rather the predetermined path or rather the stored path comprises one or more predetermined, particularly stored, path sections. In an exemplary embodiment, a path section comprises one or more predetermined, particularly saved, positions of the robot and/or their connection, which in a further development can be or can become linear, ring-shaped or (partially) circular or defined by splines. In one exemplary embodiment, a path section is or rather will be predefined by the instruction set of a control program such as LIN(x), SPLINE(x1, x2 , . . . ) or similar with positions x1, x2 ∈DOF in the work space or joint angle space and the number of degrees of freedom DOF of the robot.
In an exemplary embodiment one or rather the current path section is a current or rather the next to be traversed path section of the predetermined path. It, or rather the instruction set that defines it, can particularly be or have been selected by a set pointer, which in a further development automatically selects in succession different path sections or instruction sets, to have the predetermined path traversed by the robot, and/or manually or by operator-command can be or will be placed or switched over on/to a different or any other path section or command set.
In an exemplary embodiment, the distance of a position to a path section can depend on or be described by a particularly Cartesian or Euclidean, particularly minimal or vertical distance of the position to the path section, particularly in the work space or the joint coordinate space. In an exemplary embodiment, the distance is the quantity or rather the Euclidean norm or length of the multi-dimensional vector, particularly in the work space or the joint coordinate space, from the position on the path section, which is perpendicular to the path section.
In an exemplary embodiment, the distance parameter can be a single or multi-dimensional quantity, which depends on the distance, particularly linearly, or (mathematically) describes the distance. In a further development, the distance parameter can have or rather be a particularly weighted norm, particularly a sum of the differences between one or more or all coordinates of the robot and of the path section.
If generally a position of the robot is described by the coordinates x =[x1. . . . , xn] for example the position=[x1,=x, x2=Y, x1=z] and the orientation [x4,=α, x5=β, x6=γ] of its TCP or its joint angle [q1 , . . . , q6,], and a path section is described correspondingly by a relation, particularly a function, Y(s)=[Y1(s), . . . , Yn(s)] with the path parameter, then the distance or rather the distance parameter d(s) can particularly be defined as d(s)=Σiwi·|xi−Yi(s)| with the weighting factors wi or also a different norm, for example a maximum norm, via x, Y, particularly (x−Y) for example d(s)=Max(wi·|xi−Yi(s)). In one exemplary embodiment, the weighting factors wi are all unequal to 0, specifically equal to 1, in another exemplary embodiment one or more weighting factors wi can, with the exception of at least one weighting factor, also be equal to 0.
By identifying a deployment position that satisfies a predetermined condition, a robot may be advantageously positioned on the current path section, more specifically again or for the first time.
In an exemplary embodiment, the distance parameter meets the predetermined condition for a (deployment) position or rather the distance parameter of the (deployment) position (only) insofar as or so far as it or its value is less than or equal to the distance parameter or the value of the distance parameter for all positions in a partial area of the current path section or rather the (values of the) distance parameter(s) of all positions within a partial area of the current path section. In other words, the deployment position can be derived from a position on the current path section, which is at least as close to the current position as or closer than all positions within a partial area of the current path section. In this manner, it is possible to achieve an advantageously short movement to the deployment position. If at least two positions in a partial area of the current path section have the same minimum (values of) the distance parameter(s), then in an exemplary embodiment it is possible to select from these positions that deployment position which meets an additional requirement, particularly a position, which is closest to a beginning or end of the current path section or a stored return position or similar.
In a further development, the partial area of the current path section is complementary to the deployment position, or rather the partial area and the deployment position jointly form the current path section. In other words, in one exemplary embodiment the distance parameter of a (deployment) position satisfies the predetermined 5 conditions (only) if or as long as it is less than or equal to the distance parameter of all other positions of the current path section, particularly if or rather insofar as it is minimal. Accordingly, in an exemplary embodiment the deployment position is determined on the current path section of the predetermined path, for which (the value) of a distance parameter, which is defined on the basis of a distance of the current position of the robot to the current path section, is minimal or rather is set up as the means for determining a deployment position. In this manner, it is possible to advantageously achieve the shortest movement to the deployment position.
In an exemplary embodiment, the deployment condition can comprise a deviation of the current position of the robot from the current path section, specifically it may not be fulfilled, insofar as a deviation of the current position of the robot from the current path section is less than a predetermined, single or multi-dimensional (first) limit value, which in one exemplary embodiment n, at least within the framework of the computational and/or positioning accuracy, can be equal to or greater than zero. In one exemplary embodiment, the deviation can be defined or determined in the same manner as the distance parameter. In other words, the deployment condition in an exemplary embodiment is not fulfilled if the current position is not within the current path section.
In this way, the robot can be moved advantageously out of its current position (further) along the current path section, provided that its current position is already sufficiently close to the current path section, particularly that it lies on the current path section.
Additionally, or alternatively, the deployment condition can, particularly after a (preceding) interruption while traversing the path, comprise a deviation of a stored return position of the robot from the current path section, specifically it may not be fulfilled insofar as a deviation of the return position of the robot from the current path section is less than a predetermined, single or multi-dimensional (second) limit value
which in an exemplary embodiment, at least within the framework of the computational and/or positioning accuracy, can be equal to or greater than zero. In other words, the deployment condition in an exemplary embodiment is not fulfilled if the return position is not within the current path section.
In an exemplary embodiment, the deviation can be defined or determined in the same manner as the distance parameter. If the current path section does not (any longer) correspond to the path section on which the stored return position is located or for which it was stored or which exhibits the return position, for example, due to a modification of this path section or a jump to a different stored path section, then in an exemplary embodiment the deviation of the return position from the (new) current path section exceeds the (second) limit value. In other words, the deployment condition is not fulfilled in an exemplary embodiment, if or insofar as the current path section exhibits the stored return position.
In a further development, the return position stored will be, or rather is, a or rather the last position of the robot on the path prior to the interruption.
In this way, the robot can be advantageously moved from its current position to its last stored (return) position on the current path section, and from there can be moved on the current path section, provided that the return position is still sufficiently close to the current section, particularly that it is still located on the current path section.
In an exemplary embodiment, the robot is moved to the return position, particularly along a linear path in the work space or in the joint coordinate space and therefore advantageously on particularly a short path, if or insofar as the deviation of the return position of the robot from the current path section is less than the predetermined (second) limit, particularly (only) if or insofar as the deviation of the current position of the robot from the current path section is not less than the predetermined (first) limit. Similarly, in an exemplary embodiment the system has the means for moving to the return position, particularly on a linear path in the work space or in the joint coordinate space, if or insofar as the deviation of the return position of the robot from the current section is less than the predetermined (second) limit, particularly (only) if or insofar as the deviation of the current position of the robot from the current path section is not less than the predetermined (first) limit value.
In an exemplary embodiment, the current path section will be, or rather is, predetermined by a stored path section of the predetermined path, by means of, particularly manually given or operator commanded, modification or alteration or change, particularly substitution or replacement. In other words, the robot can be advantageously positioned on the deployment position and thus on the current path section if its current and/or return position deviates from the current path section due to a modification of the current path section.
In an exemplary embodiment, the current path section will be, or rather is, predefined by a particularly manually or operator commanded jump to a stored path section of the predetermined path. In other words, the robot can be positioned advantageously on the deployment position and thus on the (new) current path section if its current and/or return position deviates from the (previous) current position due to a jump particularly by the set pointer to another path section or instruction set.
In an exemplary embodiment, the current path section can also be a first path section of the predetermined path. In other words, the method can also be used before commencing movement, particularly the first movement or a restarted movement along the predetermined path.
In an exemplary embodiment, the robot is moved to the deployment position along a linear path in the work space or the joint coordinate space and thus advantageously on a particularly short path. Correspondingly, in an exemplary embodiment the system has the means for moving to the deployment position along a linear path in the work space or joint coordinate space.
In an exemplary embodiment, the robot is moved to the deployment position and/or the robot is driven from the deployment position to an end position or target position of the current path section on the current path section, particularly (only after) when it receives a corresponding start command. Correspondingly, in an exemplary embodiment the system has the means to enter a start command and/or means to drive the robot to the deployment position and/or an end position or target position of the current path section on the path section, particularly (only) after an appropriate start command has been given. In this way, in an exemplary embodiment, after reaching the deployment position, which can particularly be accomplished along the shortest way, it is then possible to continue moving on the predetermined path so that it can be used or utilized advantageously as much as possible.
According to one aspect of the present invention, a predetermined first path of a predetermined path group is traversed with/by a first robot of a, or rather the, robot setup in accordance with one of the methods described here, in particular with at least the deployment conditions being fulfilled the robot is moved to the deployment position, and, particularly temporally, in synchronization with this predetermined path, one or more predetermined paths of the path group is traversed with/by one or several other robots(s) of the robot setup.
A system for the at least partially automated movement along a predetermined path group with/by at least two robots according to an aspect of the present invention, particularly a system, particularly a controller, the robot arrangement, is set up by hardware means and/or software means to perform one of the methods described herein and/or has:
A system described here for the at least partially automated movement along a predetermined path with an initial one of the robots; and means for synchronously moving along one or more additional predetermined paths of the path group with one or more other robots of the robot setup.
A synchronized movement along paths is here understood to mean particularly that at least no robot overdrives a predetermined synchronization position on its predetermined path until the robot or the other robots of the robot setup have reached the synchronization positions on their predetermined path assigned to this synchronization position or synchronized with them, particularly a movement along the paths in such a way that the robots, at least essentially, in particular—within the framework of the precision of the robot or the robots—exactly simultaneously reach the synchronization positions assigned to them on their predetermined paths. This can be realized particularly by means of a corresponding Predefined speed profile—(s) with the time derivative
(s) of the path parameter s or a geometric coupling of the paths.
In an exemplary embodiment, one or several of the other robots can wait respectively at a predetermined synchronization position, for example, an end position of a path section, until the first robot reaches on the first path the synchronization position assigned to this or these synchronization position(s) after it has moved to the deployment position.
While doing so, however, it can happen that the first robot does not (any longer) reach this assigned synchronization position, for example, because this synchronization position is located on a skipped or an altered path section.
In particular therefore, in an exemplary embodiment n, synchronized (respectively) to the deployment position of the first robot, a further deployment position of the first robot or the other robots on the path or paths is determined and stopped at by the robot or the robots. A synchronized further deployment position can particularly be determined or defined in such a way that the robots in a synchronized manner, particularly simultaneously, reach at least predetermined synchronization positions on their respective predetermined paths or path sections, these synchronization positions being adjacent to the deployment positions in the direction of movement or sense of movement when they jointly start in their (synchronized) deployment positions and move along their predetermined paths, particularly when their respective predetermined paths or path sections starting out from their synchronized deployment positions are geometrically coupled.
In a further development, at least one synchronized further deployment position on the other path will be moved into. In this manner, the predetermined further path can be used advantageously. In a further development, at least one synchronized further deployment position will be moved into on a linear path in the work space or the joint coordinate space.
In this manner, the synchronized further deployment position can be advantageously moved into along the shortest path.
Accordingly, in an exemplary embodiment n the system incorporates the means to determine, synchronized to the deployment position of the first robot, a further deployment position for at least one further robot on its further path, and the means to move into these further deployment position(s) with the further robot(s), particularly on the further path (s) or on (a) linear path (s) in the work space or joint coordinate space.
A means within the sense of the present invention can be technically developed by hardware and/or software, in particular a, preferably with a memory and/or bus system, data-connected or signal-connected, in particular digital, processing unit, in particular microprocessor unit (CPU) and/or have one or more programs or program modules. The CPU can be developed to process commands that are implemented as a program stored in a storage system, to acquire data signals from a data bus and/or to send output signals to a data bus. A storage system can have one or several, in particular various storage media, in particular optical, magnetic, solid state media and/or other non-volatile media. The program can be designed in such a way that it embodies the methods described here or is capable of executing them, so that the CPU can execute the steps of such methods and thereby in particular design and/or operate the robot, and in particular control the robot or the robot setup.
In an exemplary embodiment, one or more steps of a method described herein is/are performed in a partly or fully automated way.
Other advantages and features arise from the subclaims and the exemplary embodiment examples. For this purpose, the following partly schematic figures show:
By way of example, the robot setup comprises a first robot 10 having a controller 11 and a further robot 20 with a controller 21, which together form a system for implementing a method for the synchronized movement along the path group by the two robots 10, 20 according to an exemplary embodiment n of the present invention.
By way of example, the robots 10, 20 features six axes of motion (rotation), whose positions are described by the joint coordinates q1 , . . . , q1,6 or q2,1 , . . . , p2,6. These joint coordinates or the three-dimensional position and orientation of a TCP indicated by a dot-dash line in
A path for the first robot 10 is predefined or rather stored in its controller 11, whereby the path comprises successive path sections Y1,1 , . . . , Y1,3. Each of these path sections is predefined particularly by a corresponding command set of a control program stored in the controller 11, and has an end position or target position x1,e1, x1,e2 or x1,e3.
Analogously, a path for the further robot 20 is predefined or rather stored in its controller 21, whereby the path comprises successive path sections Y2,1 , . . . , Y2,3. Analogously, each of these path sections is predefined by a corresponding command set of a control program stored in the controller 21, and has an end position or target position x2,e1,x2,e2 or x2,e3.
The predefined paths {Y1,1 , . . . , Y1,3}, {Y2,1 , . . . , Y2,3}. are traversed synchronized in such a way that the robots 10, 20 simultaneously reach the end positions of the respective path sections. In other words, in the example exemplary embodiment, the end positions are generically selected as synchronized/synchronization positions.
By way of example, the movement along the path sections was interrupted and the saved path section Y1,2, just traversed by robot 10, was modified to a new path section Y′1,2, which is indicated by dashed lines in
The current path section Ya2 of the second robot 20 is the (unchanged) saved path section Y2,2.
Due to this modification, the current position Xa1 of the first robot 10 is no longer on this current path section Ya1.
An analogous situation could result from an operator commanding a jump of the set pointer in the control program of the first robot 10 or by manually controlling the first robot 10 to move to another position.
With reference to
In a first step S10, it is determined whether an interruption of the movement of the path group has occurred or not. If there is no interruption (S10: “N”), the system or method repeats step S10.
If there is an interruption (S10: “Y”), the system or method proceeds to step S20.
In this step it checks whether a current position xa of the respective robot is still on the current path section Ya or not, by determining whether there is a deviation of the current position of the robot from the current path section, and checks whether this deviation is below a first limit value.
As explained above with reference to
In this step it checks whether, when the interruption of the movement of the path group occurred, a stored return position xn, which in the exemplary embodiment example due to the modification of the path section respectively corresponds to the current position xa, is still on the current path section Ya or not, by determining whether there is a deviation of the saved return position of the robot from the current path section, and checks whether it is less than a second limit value.
As explained above with reference to
In this step, the system or the method determines for the first robot 10 a deployment position xn on the current path section Ya1 of the predetermined path for which the distance parameter d, which is determined on the basis of a distance of the current position xai of the first robot 10 to the current path section Ya1, is minimal and thus smaller than the partial area xn of the current path section Ya1\xn that is complementary to the deployment position Ya1.
In the exemplary embodiment example, the distance parameter d, which in an exemplary embodiment is weighted by component, is the vector quantity d from the current position xai to the current path section Ya1, which is perpendicular to the current path section Ya1, as indicated in
It should again be noted that the position x respectively describes the position and orientation of the TCP in six dimensions, so that for example the position can be in the joint angle space or axis space. Accordingly, d can be calculated particularly with d=√{square root over ((d12+d22+d32+d42+52+d62))} whereby d1 , . . . , d6 represent the components of the vector d in the joint angle space or axis space.
In the same manner, position x can, again purely by example, also encompass the three position coordinates, x, y, z, and the skew-symmetric part of the transformation matrix between the TPC and an environment-fixed base coordinate system, which describes the orientation of the TPC. Accordingly, the vector d can also be represented in the work space.
The deployment position xn can particularly also be found, or rather defined, by means of a hypersphere—where appropriate, deformed by weighting factors or scaled in coordinate directions—around the current position in a common space, in which the path is predetermined or in which it is transformed, and in which the current position is known or has been determined, which is continuously enlarged until it contacts the path for the first time, whereby the contact point is then the deployment position xn.
This is followed by a step S80, in which a first robot 10 moves along a linear path in the work space or joint coordinate space and moves into the deployment position xn, as soon as it, or rather the robot setup, receives a corresponding start command.
In a step S40, the first robot 10 is then driven from the deployment position to the end position x1,e2 of the current path section Ya1 on the current path section Ya1.
On the other hand, if the test in step S50 indicates that the return position xr, which was stored at the interruption of the movement along the path group, is still lying on the respective path section Ya (S50: “Y”) because the deviation of the stored return position of the current path section is less than the second limit value, for example, because the first robot 10 was only manually moved along the unaltered path section Y1, 2 from its stored return position xr to its current position xa, then, in a step S60, this return position xr is moved into by the robot along a linear path in the work space or joint coordinate space.
In step S40, the robot is then moved from the return position xr to the end position xe of the current path section on the current path section.
If the test in step S20 shows that the current position xa is still on the current path section Ya (S20: “Y”), then the system or the method continues with step S30.
As explained above with reference to
In step S30, the system or method checks whether a deployment position xn has been determined for another robot of the robot setup.
As explained above, this is the case with respect to the other robot 20, because the deployment position xn has been determined for the first robot 10.
Accordingly (S30: “N”), the system or method continues with step S90.
In this step, for the second robot 20 it determines a further deployment position xs for the further robot 20 on the further path {Y2,1, . . . Y2,3}, this further deployment position being synchronized to the deployment position xn of the first robot. This deployment position is determined such that the first robot 10, starting from its deployment position xn on its path {Y1,1,Y′1,2,Y2,3} and the second robot 20, starting from its other deployment position xs, move along the further path {Y2,1 , . . . Y2,3}, and reach the respective next synchronization points x1,e2,x2,e2, at the same time.
Subsequently, in a step S100, the further robot on its further path {Y2,1, . . . Y2,3} moves into this further deployment position xs, as indicated in
From there, in a next step S40, the next end position is moved into, whereby in the example exemplary embodiment the end position and the synchronization position coincide for a more compact representation.
If in step S30 the system or the method detects that no deployment position xen has been determined for any other robots of the robot arrangement (S30: “N”), then the next position is moved into directly in step S40.
Although the preceding description explains exemplary embodiments, it should be noted that a large number of variations are possible.
Thus, the method was explained by example for two synchronized robot 10, 20.
If it is now performed for a single robot, for example, the first robot 10, then steps S30, S90 and S100 can be eliminated, or rather the next end position can be moved into directly if it is determined that the current position is still on the current path section (S20: “Y”).
In addition, or alternatively, step S50 can also be eliminated, i.e. if there is a deviation between the current position of the current path section, then a deployment position can be determined and moved into—where applicable, only after a (further) start command has been received.
It should also be noted that the exemplary embodiments are mere examples only, and in no way at all do they limit the scope of protection, the applications and the structure. Rather, the specialist will find in the preceding description a guide for establishing at least one exemplary embodiment, whereby various changes, particularly with respect to the function and arrangement of the described components may be made without departing from the scope of protection as derived from the claims and these equivalent feature combinations.
While the present invention has been illustrated by a description of various embodiments, and while these embodiments have been described in considerable detail, it is not intended to restrict or in any way limit the scope of the appended claims to such detail. The various features shown and described herein may be used alone or in any combination. Additional advantages and modifications will readily appear to those skilled in the art. The invention in its broader aspects is therefore not limited to the specific details, representative apparatus and method, and illustrative example shown and described. Accordingly, departures may be made from such details without departing from the spirit and scope of the general inventive concept.
Number | Date | Country | Kind |
---|---|---|---|
10 2015 008 188.8 | Jun 2015 | DE | national |
Filing Document | Filing Date | Country | Kind |
---|---|---|---|
PCT/EP2016/001050 | 6/20/2016 | WO |
Publishing Document | Publishing Date | Country | Kind |
---|---|---|---|
WO2016/206798 | 12/29/2016 | WO | A |
Number | Name | Date | Kind |
---|---|---|---|
4433382 | Cunningham | Feb 1984 | A |
4568816 | Casler, Jr. | Feb 1986 | A |
4617502 | Sakaue | Oct 1986 | A |
4675502 | Haefner | Jun 1987 | A |
4733040 | Pelloni | Mar 1988 | A |
5084826 | Hariki | Jan 1992 | A |
5086262 | Hariki | Feb 1992 | A |
5243266 | Kasagami | Sep 1993 | A |
5254923 | Kanitani | Oct 1993 | A |
5467003 | Kosaka | Nov 1995 | A |
5530791 | Okabayashi | Jun 1996 | A |
5545960 | Ishikawa | Aug 1996 | A |
5758298 | Guldner | May 1998 | A |
5815399 | Fujibayashi | Sep 1998 | A |
5889924 | Okabayashi | Mar 1999 | A |
6004016 | Spector | Dec 1999 | A |
6004019 | Suita | Dec 1999 | A |
6040554 | Terada | Mar 2000 | A |
6134486 | Kanayama | Oct 2000 | A |
6303890 | Scuderi | Oct 2001 | B1 |
6330493 | Takahashi | Dec 2001 | B1 |
6374155 | Wallach | Apr 2002 | B1 |
6442451 | Lapham | Aug 2002 | B1 |
6489741 | Genov | Dec 2002 | B1 |
6556891 | Hietmann | Apr 2003 | B2 |
6748325 | Fujisaki | Jun 2004 | B1 |
6804580 | Stoddard | Oct 2004 | B1 |
6897626 | Fujibayashi | May 2005 | B2 |
7010390 | Graf | Mar 2006 | B2 |
7024250 | Graf | Apr 2006 | B2 |
7069112 | Graf | Jun 2006 | B2 |
7076322 | Chandhoke | Jul 2006 | B2 |
7085624 | Aldred | Aug 2006 | B2 |
7110859 | Shibata | Sep 2006 | B2 |
7130718 | Gunnarsson | Oct 2006 | B2 |
7149606 | Krause | Dec 2006 | B2 |
7174474 | Low | Feb 2007 | B1 |
7209801 | Anfindsen | Apr 2007 | B2 |
7211978 | Chang | May 2007 | B2 |
7251548 | Herz | Jul 2007 | B2 |
7395606 | Crampton | Jul 2008 | B2 |
7421314 | Stoddard | Sep 2008 | B2 |
7443124 | Bischoff | Oct 2008 | B2 |
7558646 | Matsumoto | Jul 2009 | B2 |
7620478 | Fortell | Nov 2009 | B2 |
7627394 | Volcic | Dec 2009 | B2 |
7653977 | Wiedemann | Feb 2010 | B2 |
7680547 | Liu | Mar 2010 | B2 |
7729804 | Matsumoto | Jun 2010 | B2 |
7860609 | Yanagita | Dec 2010 | B2 |
7865277 | Larson | Jan 2011 | B1 |
7957838 | Poljen | Jun 2011 | B2 |
7974737 | Tilove | Jul 2011 | B2 |
8185265 | Nagano | May 2012 | B2 |
8204623 | Bhattacharyya | Jun 2012 | B1 |
8239083 | Durkos | Aug 2012 | B2 |
8271131 | Kato | Sep 2012 | B2 |
8290620 | Yoshizawa | Oct 2012 | B2 |
8340820 | Nair | Dec 2012 | B2 |
8386110 | Maekawa | Feb 2013 | B2 |
8392065 | Tolstedt | Mar 2013 | B2 |
8588981 | Fortell | Nov 2013 | B2 |
8639364 | Stoddard | Jan 2014 | B2 |
8930009 | Miyoshi | Jan 2015 | B2 |
8972061 | Rosenstein | Mar 2015 | B2 |
9102060 | Tarragona | Aug 2015 | B2 |
9192869 | Moriya | Nov 2015 | B2 |
9354626 | Boerner | May 2016 | B2 |
9381645 | Yarlagadda | Jul 2016 | B1 |
9408515 | Rosenstein | Aug 2016 | B2 |
9411335 | Kim | Aug 2016 | B2 |
9573273 | Takeda | Feb 2017 | B2 |
9632493 | Negre | Apr 2017 | B2 |
9821456 | Riedel | Nov 2017 | B2 |
9895807 | Wiedemann | Feb 2018 | B2 |
9943964 | Hares | Apr 2018 | B2 |
10179406 | Dalibard | Jan 2019 | B2 |
10239206 | Negishi | Mar 2019 | B2 |
10394216 | Krause | Aug 2019 | B2 |
10426560 | Bowling | Oct 2019 | B2 |
10780582 | Pinter | Sep 2020 | B2 |
10836038 | Sun | Nov 2020 | B2 |
11065766 | Sedlmayr | Jul 2021 | B2 |
11110605 | Zanchettin | Sep 2021 | B2 |
11169523 | Oh | Nov 2021 | B2 |
12042805 | Kunz | Jul 2024 | B2 |
20030025472 | Jones | Feb 2003 | A1 |
20030216834 | Allard | Nov 2003 | A1 |
20030220715 | Kneifel, II | Nov 2003 | A1 |
20040030452 | Graf | Feb 2004 | A1 |
20040030453 | Graf | Feb 2004 | A1 |
20040093119 | Gunnarsson | May 2004 | A1 |
20040111185 | Gmeiner | Jun 2004 | A1 |
20040135779 | Inukai | Jul 2004 | A1 |
20040138779 | Shibata | Jul 2004 | A1 |
20040172164 | Habibi | Sep 2004 | A1 |
20040193321 | Anfindsen | Sep 2004 | A1 |
20040199290 | Stoddard | Oct 2004 | A1 |
20040230340 | Fukuchi | Nov 2004 | A1 |
20040254677 | Brogardh | Dec 2004 | A1 |
20050107921 | Watanabe | May 2005 | A1 |
20050131581 | Sabe | Jun 2005 | A1 |
20050165508 | Kanda | Jul 2005 | A1 |
20060149421 | Akiyama | Jul 2006 | A1 |
20060200254 | Krause | Sep 2006 | A1 |
20060217841 | Matsumoto | Sep 2006 | A1 |
20070019029 | Hiruma | Jan 2007 | A1 |
20070030271 | Kamiya | Feb 2007 | A1 |
20070142967 | Volcic | Jun 2007 | A1 |
20080009964 | Bruemmer | Jan 2008 | A1 |
20080009965 | Bruemmer | Jan 2008 | A1 |
20080009966 | Bruemmer | Jan 2008 | A1 |
20080009967 | Bruemmer | Jan 2008 | A1 |
20080009968 | Bruemmer | Jan 2008 | A1 |
20080009969 | Bruemmer | Jan 2008 | A1 |
20080009970 | Bruemmer | Jan 2008 | A1 |
20080114492 | Miegel | May 2008 | A1 |
20080154457 | Yu | Jun 2008 | A1 |
20090018690 | Negre | Jan 2009 | A1 |
20090198378 | Boerner | Aug 2009 | A1 |
20090228166 | Durkos | Sep 2009 | A1 |
20090234527 | Ichinose | Sep 2009 | A1 |
20090326713 | Moriya | Dec 2009 | A1 |
20100008754 | Hartmann | Jan 2010 | A1 |
20100063663 | Tolstedt | Mar 2010 | A1 |
20100063680 | Tolstedt | Mar 2010 | A1 |
20100094481 | Anderson | Apr 2010 | A1 |
20100152944 | Kouno | Jun 2010 | A1 |
20100198402 | Greer | Aug 2010 | A1 |
20100235033 | Yamamoto | Sep 2010 | A1 |
20100241289 | Sandberg | Sep 2010 | A1 |
20110009238 | Baba | Jan 2011 | A1 |
20110035087 | Kim | Feb 2011 | A1 |
20110054689 | Nielsen | Mar 2011 | A1 |
20110125324 | Baek | May 2011 | A1 |
20110153080 | Shapiro | Jun 2011 | A1 |
20110226282 | Choi | Sep 2011 | A1 |
20110288667 | Noda | Nov 2011 | A1 |
20120165982 | Kim | Jun 2012 | A1 |
20120185089 | Schreiber | Jul 2012 | A1 |
20120209428 | Mizutani | Aug 2012 | A1 |
20120215351 | McGee | Aug 2012 | A1 |
20120215352 | Eberst | Aug 2012 | A1 |
20120232738 | Jeon | Sep 2012 | A1 |
20120313779 | Papaefstathiou | Dec 2012 | A1 |
20130116880 | Shitamoto | May 2013 | A1 |
20130238170 | Klinger | Sep 2013 | A1 |
20130345867 | Wiedemann | Dec 2013 | A1 |
20140124004 | Rosenstein | May 2014 | A1 |
20150073593 | Hamm et al. | Mar 2015 | A1 |
20150148958 | Primessnig | May 2015 | A1 |
20150239121 | Takeda | Aug 2015 | A1 |
20150239123 | Hagenauer et al. | Aug 2015 | A1 |
20150277398 | Madvil | Oct 2015 | A1 |
20150278406 | Embon | Oct 2015 | A1 |
20150321349 | Hazan | Nov 2015 | A1 |
20150336267 | Sun | Nov 2015 | A1 |
20160031082 | Hazan | Feb 2016 | A1 |
20160031083 | Embon | Feb 2016 | A1 |
20160034613 | Hazan | Feb 2016 | A1 |
20160167652 | Slusar | Jun 2016 | A1 |
20170028556 | Summer | Feb 2017 | A1 |
20170036232 | Hoffman | Feb 2017 | A1 |
20170080565 | Dalibard | Mar 2017 | A1 |
20170199525 | Albaghajati | Jul 2017 | A1 |
20170245955 | Bowling | Aug 2017 | A1 |
20170347979 | Fehre | Dec 2017 | A1 |
20180178383 | Burkhart | Jun 2018 | A1 |
20180281191 | Sinyavskiy | Oct 2018 | A1 |
20190184571 | Hou | Jun 2019 | A1 |
20190202055 | Wang | Jul 2019 | A1 |
20190210224 | Zanchettin | Jul 2019 | A1 |
20190263393 | Han | Aug 2019 | A1 |
20210129999 | Tsaliah | May 2021 | A1 |
20210252707 | Wang | Aug 2021 | A1 |
20230356399 | So | Nov 2023 | A1 |
20230384444 | Yaguma | Nov 2023 | A1 |
20240319745 | Tsaliah | Sep 2024 | A1 |
Number | Date | Country |
---|---|---|
1507384 | Jun 2004 | CN |
1990197 | Jul 2007 | CN |
103433925 | Dec 2013 | CN |
103513656 | Jan 2014 | CN |
104423318 | Mar 2015 | CN |
104684695 | Jun 2015 | CN |
3711020 | Oct 1988 | DE |
102008007438 | Nov 2012 | DE |
0425959 | May 1991 | EP |
0696493 | Feb 1996 | EP |
0696493 | Sep 1998 | EP |
2014019706 | Feb 2014 | WO |
2014135175 | Sep 2014 | WO |
Entry |
---|
European Patent Office; Search Report in International Patent Application No. PCT/EP2016/001050 published Dec. 29, 2016; 10 pages. |
German Patent Office; Office Action in related German Patent Application No. 10 2015 008 188.8 dated Oct. 22, 2015; 4 pages. |
Chinese Patent Office; Office Action in related Chinese Patent Application No. 201680037192.0 dated Apr. 2, 2020; 7 pages. |
Chinese Patent Office; Search Report in related Chinese Patent Application No. 201680037192.0 dated Mar. 28, 2020; 3 pages. |
European Patent Office; Office Action in related European Patent Application No. 16 731 512.6 dated Jun. 8, 2021; 5 pages. |
European Patent Office; Office Action in related European Patent Application No. 16 731 512.6 dated Jun. 15, 2023; 7 pages. |
Number | Date | Country | |
---|---|---|---|
20180178383 A1 | Jun 2018 | US |