Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
How to find the actual working space of the robot?
#1
Hi, RoboDK team

I want to use software to find out the actual working range of the robot in the workstation.

After the construction completed, I know that the robot's working range can be viewed by pressing the "*" key, but in fact it will collide with objects in the workstation, so the check collisions function must be used. During the simulation, I encountered the following problems:

1. I have also watched this part of the demo video on Youtube, i want to know, this "create collision-free map" function must be based on the prerequisite of the specified path (add the HOME & Target point)? 

2. I used it directly without adding motion points and programs, and found that it seems that the motion of the robot does not take obstacles into consideration at all. For example, the path below is outside the ceiling. XD
   

3. Why is my simulation only the collision detection of the robot itself? The working head on the robot flange should naturally be taken into consideration, but when I moved to the working head and collided with obstacles, the software did not alarm, until the robot itself.
         

I`m looking forward to answers.

Best regards!

Van
#2
Hi Van,

Regarding your last question, make sure that you actually verify collision with the tool by opening the collision map.

Follow this link for more details:
https://robodk.com/doc/en/Collision-Avoi...Collisions

Jeremy
Find useful information about RoboDK and its features by visiting our Online Documentation and by watching tutorials on our Youtube Channel


#3
(11-30-2020, 08:07 PM)Jeremy Wrote: Hi Van,

Regarding your last question, make sure that you actually verify collision with the tool by opening the collision map.

Follow this link for more details:
https://robodk.com/doc/en/Collision-Avoi...Collisions

Jeremy

Thanks a lot, Jeremy

I checked the collision map and found that the tool detection is turned off by default.

So what do you think of the main problem? I mean how can i use RoboDK to find the actual working range of a robot with tools in a workstation? 

Van
  




Users browsing this thread:
1 Guest(s)