Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5

Non-blocking movements simulation and real robot do not match

#1
I want to trigger the robot.Stop() command during a non-blocking moveL or moveJ in both simulation and real robot movements. In the RoboDK simulation the robot stops moving during a non-blocking movement when triggering the Stop() command as expected. However, the real robot only stops after completing a certain movement so it does not seem that the non-blocking movements from the simulation are processed correctly by the real robot (ABB IRB 1200-5/0.9).

Do you have any suggestions on how to create non-blocking movements for the robot as well? Or how to match non-blocking movements with the simulation in RoboDK as a digital twin? Thank you in advance!
#2
Not all drivers support stopping the movement after it has started (even if the RoboDK simulation stops). This applies to ABB controllers.

We'll try to improve this in future versions so we can interrupt the movement for ABB robots with the Stop command.
#3
(02-22-2023, 09:48 AM)Albert Wrote: Not all drivers support stopping the movement after it has started (even if the RoboDK simulation stops). This applies to ABB controllers.

We'll try to improve this in future versions so we can interrupt the movement for ABB robots with the Stop command.
Thank you for your response!
#4
A workaround for now would be to split your programs into smaller step size (this can be done by RoboDK itself) so that the Stop command returns faster.
Please read the Forum Guidelines before posting!
Find useful information about RoboDK by visiting our Online Documentation.
#5
(02-22-2023, 09:48 AM)Albert Wrote: Not all drivers support stopping the movement after it has started (even if the RoboDK simulation stops). This applies to ABB controllers.

We'll try to improve this in future versions so we can interrupt the movement for ABB robots with the Stop command.

Hi Albert,

What about the drivers for the Kuka KR 150 R2700-2 & CR5 controller? Do they support stopping the movement after it has started?

(02-22-2023, 06:42 PM)Sam Wrote: A workaround for now would be to split your programs into smaller step size (this can be done by RoboDK itself) so that the Stop command returns faster.

Hi Sam,

Thank you for your response. Is this also possible via Python API?
#6
It is possible to do this through the API with the latest version of RoboDK by using the ProgMaxLines command.

Example:
Code:
RDK.Command("ProgMaxLines", 4000)
  




Users browsing this thread:
1 Guest(s)