1 / 23

Deadlock-Free and Collision-Free Coordination of Two Robot Manipulators

Deadlock-Free and Collision-Free Coordination of Two Robot Manipulators. Presented by Huy Nguyen April 28, 2003. Introduction. Goal Coordinate the trajectories of two robot manipulators so as to avoid collisions and deadlock . Definitions path – Curve in C-space.

vanya
Download Presentation

Deadlock-Free and Collision-Free Coordination of Two Robot Manipulators

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Deadlock-Free and Collision-Free Coordination of Two Robot Manipulators Presented by Huy Nguyen April 28, 2003

  2. Introduction Goal • Coordinate the trajectories of two robot manipulators so as to avoid collisions and deadlock. Definitions • path – Curve in C-space. • trajectory – Time history of positions along path (curve in state space).

  3. The Approach Patrick A. O’Donnell and Tomas Lozano-Perez ’89 • Decouple path specification step from trajectory specification step. • Assume path of each manipulator has been planned off-line and is composed of a sequence of path segments. • Assume that we can estimate the time required to execute each segment. Trajectory coordination problem is a scheduling problem where space is the shared resource.

  4. Task-Completion (TC) Diagram Task-Completion Diagram Path in C-Space gB gB gA B sA sB sA gA sB A

  5. Task-Completion (TC) Diagram gB B sB sA gA A

  6. Task-Completion (TC) Diagram • Axes represent segments of robot paths. gB B sB sA gA A

  7. Task-Completion (TC) Diagram • Axes represent segments of robot paths. • Rectangle Rij is shaded if the swept volume of the ith path segment of A collides with swept volume of jth path segment of B. gB B sB sA gA A

  8. Task-Completion (TC) Diagram • Axes represent segments of robot paths. • Rectangle Rij is shaded if the swept volume of the ith path segment of A collides with swept volume of jth path segment of B. • A schedule is a non-decreasing curve that connects lower-left corner of diagram to top-right corner. gB B sB sA gA A

  9. Task-Completion (TC) Diagram • Axes represent segments of robot paths. • Rectangle Rij is shaded if the swept volume of the ith path segment of A collides with swept volume of jth path segment of B. • A schedule is a non-decreasing curve that connects lower-left corner of diagram to top-right corner. • A safe schedule is a schedule that never penetrates interior of union of collision rectangles. gB B sB sA gA A

  10. Task-Completion (TC) Diagram • Axes represent segments of robot paths. • Rectangle Rij is shaded if the swept volume of the ith path segment of A collides with swept volume of jth path segment of B. • A schedule is a non-decreasing curve that connects lower-left corner of diagram to top-right corner. • A safe schedule is a schedule that never penetrates interior of union of collision rectangles. • Boundaries of collision rectangles are safe! gA A sA sB gB B

  11. Greedy Scheduler Demo procedure Greedy Scheduler; begin i:=0; j:=0; whilei < m or j < n do begin ifRi,j is collision free then begin ifi < mthen begin Execute Ai; i:=i+1; end ifj < nthen begin Execute Bj; j:=j+1; end end else ifi < m and Ri,j-1 is collision free then begin Execute Ai; i:=i+1; end else ifj < n and Ri-1,j is collision free then begin Execute Bj; j:=j+1; end Wait for any completion signals; end end gB B sB sA gA A

  12. Greedy Scheduler Demo procedure Greedy Scheduler; begin i:=0; j:=0; whilei < m or j < n do begin ifRi,j is collision free then begin ifi < mthen begin Execute Ai; i:=i+1; end ifj < nthen begin Execute Bj; j:=j+1; end end else ifi < m and Ri,j-1 is collision free then begin Execute Ai; i:=i+1; end else ifj < n and Ri-1,j is collision free then begin Execute Bj; j:=j+1; end Wait for any completion signals; end end gB B sB sA gA A

  13. Greedy Scheduler Demo procedure Greedy Scheduler; begin i:=0; j:=0; whilei < m or j < n do begin ifRi,j is collision free then begin ifi < mthen begin Execute Ai; i:=i+1; end ifj < nthen begin Execute Bj; j:=j+1; end end else ifi < m and Ri,j-1 is collision free then begin Execute Ai; i:=i+1; end else ifj < n and Ri-1,j is collision free then begin Execute Bj; j:=j+1; end Wait for any completion signals; end end gB B sB sA gA A

  14. Deadlock • Greedy Scheduler can become Deadlocked. gB B sB sA gA A

  15. SW-closure • Can avoid deadlock by computing SW-closure of union of collision regions to fills in non-convexities. . gB B sB sA gA A

  16. Parallelism • Previously, we could only execute one segment of A and/or B at each step. • Parallelism decreases execution time. • Axes correspond to expected execution time. • Want a nearly diagonal path. B A

  17. Increasing Potential Parallelism • TC Diagram may have collision regions near diagonal because of original choice of paths. B A

  18. Increasing Potential Parallelism • For a problematic collision region, replan path between the initial and final points of A by using swept volume of B as an obstacle. B B A A New path may change collision rectangles and/or execution times.

  19. Changing Tasks • Allow one robot to deal with significant delay in the other. • Construct TC diagram assuming each robot will carry out all tasks. • Allow jumps to nonadjacent regions (assume end of one cycle is beginning of another. B A

  20. Conclusions • Interesting Ideas • Decoupling of path and trajectory planning. • Interpretation as scheduling problem and use of the Task-Completion diagram. • Only use space-time planning for collisions near diagonal to increase parallelism. • Questions/Concerns • Scalability. Computing all potential collisions is expensive. • Actual results? Comparisons?

  21. End Special thanks to Chris Clark and Guha Jayachandran for the diagrams!

  22. Previous Approaches • Global Methods • Construct complete collision-free trajectories. • Example • Construct Configuration Space-Time and compute trajectories for each robot one at a time, using swept volume (in space-time) of previous trajectories as obstacles. • Pros • Guarantee that robots will reach goal. • Cons • Depends on carefully controlled trajectories.

  23. Previous Approaches • Local Methods • Decide at each point in time the trajectory for each robot. • Example • At each point in time, define separating planes and ensure that objects stay on opposite sides. • Pros • Can accommodate unexpected variations in trajectories or unexpected obstacles. • Cons • May reach deadlock. • Rely on changing paths to avoid collisions.

More Related