Different versions of RoboDK may behave differently

b05611018 · (This post was last modified: 10-16-2025, 08:33 AM by Albert.)

I wrote a python code to automatically generate the machining settings. In RoboDk 5.8.0, it worked fine. However, in 5.4.3, it showed the error about the robot stopped by user.

The information of my environment:
The robot is ABB IRB 1200-7/0.7
The frame of WC is

Code:
[    0.000000,    -1.000000,    0.000000,    0.000000 ;

      1.000000,    0.000000,    0.000000,    0.000000 ;

      0.000000,    0.000000,    1.000000,    0.000000 ;

      0.000000,    0.000000,    0.000000,    1.000000 ];

x_calib is a point object, and its parent is WC.

[  1136.300049,  -596.500000,  571.721008 ];

T9 is tool object

[    0.000000,    0.000000,    1.000000,    74.200000 ;

      0.000000,    1.000000,    0.000000,    0.000000 ;

    -1.000000,    0.000000,    0.000000,    32.200000 ;

      0.000000,    0.000000,    0.000000,    1.000000 ];

The frame of WK is 

[    1.000000,    0.000000,    0.000000,    -0.000000 ;

      0.000000,    1.000000,    0.000000,  646.867000 ;

      0.000000,    0.000000,    1.000000,  127.287000 ;

      0.000000,    0.000000,    0.000000,    1.000000 ];

x_start_p is a target, and its parent is WK

[    1.000000,    -0.000000,    0.000000,  770.388998 ;

    -0.000000,    -1.000000,    0.000000,  269.138999 ;

    -0.000000,    -0.000000,    -1.000000,  436.093001 ;

      0.000000,    0.000000,    0.000000,    1.000000 ];

The robot joints of x_start_p is
20.731027, 12.389657, 38.163011, 0.000000, 39.447332, -159.268973

**Albert** · 10-14-2025, 06:18 AM

The scenario you described should not provoke the robot to stop. This may have been the case with previous versions of RoboDK but was probably fixed a while ago.

Are you moving the robot at the same time? Are you connected to the real robot controller or just run it in simulation?

If you can share your RoboDK project file we may be able to take a better look by reproducing this specific scenario.

b05611018 · 10-14-2025, 06:41 AM

I only run it in simulation. It would report error in v5.4.3 and v5.4.1.

Here is the file. However, some parts of this file have been removed due to confidentiality. I hope this file can find out why this error happen.

Thanks!

**Albert** · 10-16-2025, 08:33 AM

I don't see multi-threading in your project. Were you altering values manually and it forced the robot to stop?

Either way, this issue was probably fixed a while ago because changing the robot machining settings without updating your program should not alter the robot movement.