RoboDK Forum - RoboDK bugs

Free license Error

Mon, 06 Apr 2026 00:12:26 +0000

I just installed the program, but every time I open it, this message shows up, and the program shuts down. I have already allowed it past the firewall. Still no improvement. Free license btw.

Screenshot 2026-04-06 010600.png (Size: 15.67 KB / Downloads: 53)

Issue with Welding Approach/Retract Angles: Solid Edge vs. SolidWorks

Wed, 18 Mar 2026 03:57:09 +0000

Hello everyone,
I hope you are all doing well.
I am experiencing an issue with the approach and retract settings when generating welding paths using the Solid Edge plugin, and I was wondering if anyone has encountered something similar.

The Context:
I currently use SolidWorks with the RoboDK plugin to export models and curves for welding programming. With my current configurations in SolidWorks, the export works perfectly. By selecting the two reference faces and the edge, I get a consistent 45-degree approach and retract angle as expected.

The Problem:
When using Solid Edge, I cannot achieve the same result, even when mirroring the exact same settings used in SolidWorks. While the model and curves export successfully, the approach and retract behavior is incorrect:
The surface normals seem to point in only one direction.
In some cases, the normals flip or vary their position along the path.
I have attached screenshots of my current settings and the resulting behavior in RoboDK for reference.
Has anyone faced this inconsistency between the two plugins? Any advice on how to get the Solid Edge export to respect the 45-degree orientation correctly would be greatly appreciated.
Thank you in advance!

Robodk_Solidedge_issues_normals.zip (Size: 619.55 KB / Downloads: 25)

Installing RoboDK on Windows 7 does not work

Sun, 08 Mar 2026 08:34:38 +0000

I installed the latest version of RoboDK but it does not work.

falloiniciorobodk.jpg (Size: 37.93 KB / Downloads: 96)

Import all.prm from robot XRC Yaskawa controller

Thu, 26 Feb 2026 14:09:40 +0000

when i try to import all.prm to yaskawa robot fail.

2026-02-26 15_07_41-RoboDK - Nueva Estación (1) - Free (Limited).png (Size: 17.59 KB / Downloads: 83)

Motoman motion problem with nx100 control box

Sun, 08 Feb 2026 07:18:50 +0000

Helló, problémám van a RoboDK-kal a Motoman UP350N és az nx100 vezérlődoboz között. Azt hiszem, a posztprocesszor nem működik megfelelően. A szimuláció tökéletesen fut, de amikor a programot a robotnak küldöm, néha nem követi az útvonalat. Tudnál segíteni, mielőtt megveszem ezt a szoftvert?

Hello, I have a problem with RoboDK between Motoman UP350N and nx100 control box. I think the post processor is not working properly. The simulation runs perfectly, but when I send the program to the robot, sometimes it does not follow the path. Can you help me before I buy this software?

RoboDK crashes when it starts

Mon, 26 Jan 2026 12:37:50 +0000

Hi
I have an issue on RoboDK crashing all the time when it starts.
I have tried to uninstall it and re install again, but it did not help. It says it loaded 2 plugins and it crashes.
I am working win11, it works perfect ok until today suddenly it starts crashing.

What can i do now? any suggestion for me, thanks for help.

best
Chen

I have tried to open RoboDK-Safe-Start.bat and it can not open it. And i have tried RoboDK-Safe-Start-D3D.bat, it works for me. But my problem is when I use CAD pluginm it will open RoboDK with normal start, it crashed again. So I don't know how to fix it, pls help me with some suggestions, thanks a lot.

best
Chen

Problem solved, GPU driver updated >D
Chen

Screenshot 2026-01-26 133729.png (Size: 73.5 KB / Downloads: 90)

Windows 11 trial app crashes every time I open

Thu, 15 Jan 2026 20:33:44 +0000

Hello, I downloaded a trial version for Windows 11. The app crashes almost immediately every time I try to open from the normal app or from the safe batch files. I have followed every forum in here on resolution including updating to the latest graphics card driver for Windows 11. Could you please help? Here is the debug file:

Code:
13:49.582 (+0 ms): RoboDK v5.9.5 debug file RoboDK.debug.txt, started on 15-01-2026-14:13:49.582

13:49.582 (+0 ms): Debug: OS:  WIN64

13:49.582 (+0 ms): Debug: Date build:  Jan  3 2026

13:49.582 (+0 ms): Debug: Qt Version (compiled):  5.15.10

13:49.582 (+0 ms): Debug: Qt Version libs in use (runtime):  5.15.10

13:49.582 (+0 ms): Debug: Main process ID:  1468

13:49.582 (+0 ms): Debug: Thread ID:  0x235c

13:49.629 (+47 ms): Debug: Processing event...

13:49.629 (+0 ms): Debug: Starting RobotTools...

13:49.629 (+0 ms): Debug: Loading settings...

13:49.629 (+0 ms): Debug: Setting up default settings...

13:49.629 (+0 ms): Debug: Default settings set

13:49.629 (+0 ms): Debug: Reading saved settings...

13:49.641 (+12 ms): Debug: Failed to get parameter from ini file

13:49.641 (+0 ms): Debug: Failed to get parameter from ini file

13:49.641 (+0 ms): Debug: Settings loaded

13:49.647 (+6 ms): Warning: link #SVGID_83_ is undefined!

13:49.647 (+0 ms): Warning: link #SVGID_83_ is undefined!

13:49.647 (+0 ms): Warning: link #SVGID_83_ is undefined!

13:49.647 (+0 ms): Warning: link #SVGID_50_ is undefined!

13:49.647 (+0 ms): Warning: link #SVGID_83_ is undefined!

13:49.647 (+0 ms): Warning: link #SVGID_50_ is undefined!

13:49.647 (+0 ms): Warning: link #SVGID_83_ is undefined!

13:49.647 (+0 ms): Warning: link #SVGID_50_ is undefined!

13:49.661 (+14 ms): Debug: Lang file not found:  "C:/RoboDK/Lang/qt_en.qm"

13:49.661 (+0 ms): Debug: Statusbar:  "Language set to English"

13:49.661 (+0 ms): Debug: Updating recent files menu...

13:49.677 (+16 ms): Debug: Created language menu

13:49.695 (+18 ms): Debug: Setting slider style...

13:49.695 (+0 ms): Debug: Done

13:49.705 (+10 ms): Debug: Image_Mix Warning 2nd image is larger  ":/img/python.svg"  ":/img/tagadd.png"

13:49.710 (+5 ms): Debug: Trying to set up SpaceMouse...

13:49.710 (+0 ms): Debug: SpaceMouse setup done

13:49.725 (+15 ms): Debug: Setting up graphics...

13:49.725 (+0 ms): Debug: Setting up main window...

13:49.741 (+16 ms): Debug: Starting main window...

13:49.761 (+20 ms): Debug: LC start...

13:49.761 (+0 ms): Debug: LC message:  LC device not found

13:49.761 (+0 ms): Debug: Dongle not found or cannot read

13:49.761 (+0 ms): Debug: LC start...

13:49.761 (+0 ms): Debug: LC message:  LC device not found

13:49.761 (+0 ms): Debug: Dongle not found or cannot read

13:49.769 (+8 ms): Debug: Loading plugin:  "CollisionFreePlanner"

13:49.769 (+0 ms): Debug: "AddinManager.dll"

13:49.771 (+2 ms): Debug: "AppLoader.dll"

13:49.772 (+1 ms): Debug: "CollisionFreePlanner.dll"

13:49.773 (+1 ms): Debug: Loading plugin file:  "CollisionFreePlanner.dll"

13:49.773 (+0 ms): Debug: Loading plugin  "CollisionFreePlanner"

13:49.773 (+0 ms): Debug: Using settings:  ""

13:49.773 (+0 ms): Debug: Setting up the status bar

13:49.777 (+4 ms): Debug: Inserting menu at the end of the utilities menu

13:49.777 (+0 ms): Debug: Setting up the menu bar

13:49.778 (+1 ms): Debug: "OPC-UA.dll"

13:49.779 (+1 ms): Debug: "PluginAttachObject.dll"

13:49.779 (+0 ms): Debug: "PluginAttachView.dll"

13:49.780 (+1 ms): Debug: "PluginDisplayPanel.dll"

13:49.781 (+1 ms): Debug: "PluginIOMonitor.dll"

13:49.781 (+0 ms): Debug: "PluginLockTCP.dll"

13:49.782 (+1 ms): Debug: "PostProcessorEditor.dll"

13:49.783 (+1 ms): Debug: "RobotPilot.dll"

13:49.783 (+0 ms): Debug: List of LOADED plugins:

13:49.783 (+0 ms): Debug:      "CollisionFreePlanner"

13:49.783 (+0 ms): Debug: Done list of plugins

13:49.783 (+0 ms): Debug: Loading plugin:  "AddinManager"

13:49.783 (+0 ms): Debug: "AddinManager.dll"

13:49.784 (+1 ms): Debug: Loading plugin file:  "AddinManager.dll"

13:49.810 (+26 ms): Warning: link #SVGID_83_ is undefined!

13:49.810 (+0 ms): Warning: link #SVGID_50_ is undefined!

13:50.015 (+205 ms): Debug: "AppLoader.dll"

13:50.015 (+0 ms): Debug: "CollisionFreePlanner.dll"

13:50.015 (+0 ms): Debug: "OPC-UA.dll"

13:50.015 (+0 ms): Debug: "PluginAttachObject.dll"

13:50.015 (+0 ms): Debug: "PluginAttachView.dll"

13:50.015 (+0 ms): Debug: "PluginDisplayPanel.dll"

13:50.016 (+1 ms): Debug: "PluginIOMonitor.dll"

13:50.016 (+0 ms): Debug: "PluginLockTCP.dll"

13:50.016 (+0 ms): Debug: "PostProcessorEditor.dll"

13:50.016 (+0 ms): Debug: "RobotPilot.dll"

13:50.016 (+0 ms): Debug: List of LOADED plugins:

13:50.016 (+0 ms): Debug:      "CollisionFreePlanner"

13:50.016 (+0 ms): Debug:      "Addin Manager"

13:50.016 (+0 ms): Debug: Done list of plugins

13:50.016 (+0 ms): Debug: Statusbar:  "Loaded 2 plugins"

13:50.016 (+0 ms): Debug: Reading preferred layout settings...

13:50.016 (+0 ms): Debug: Done

13:50.016 (+0 ms): Debug: Closing splash window

13:50.017 (+1 ms): Debug: Updating window title...

13:50.017 (+0 ms): Debug: Entering main loop

13:50.042 (+25 ms): Warning: Vertex shader for simpleShaderProg (MainVertexShader & PositionOnlyVertexShader) failed to compile

13:50.042 (+0 ms): Warning: Fragment shader for simpleShaderProg (MainFragmentShader & ShockingPinkSrcFragmentShader) failed to compile

13:50.044 (+2 ms): Warning: QGLShaderProgram: shader programs are not supported

13:50.044 (+0 ms): Critical: Errors linking simple shader: 

13:50.044 (+0 ms): Warning: Vertex shader for blitShaderProg (MainWithTexCoordsVertexShader & UntransformedPositionVertexShader) failed to compile

13:50.044 (+0 ms): Warning: Fragment shader for blitShaderProg (MainFragmentShader & ImageSrcFragmentShader) failed to compile

13:50.044 (+0 ms): Warning: QGLShaderProgram: shader programs are not supported

13:50.044 (+0 ms): Critical: Errors linking blit shader: 

-> Solution: Please install your graphics card drivers. If you are running on a Virtual Machine (VM) or your PC can't process graphics card, please start RoboDK by running this file:

    C:/RoboDK/RoboDK-Safe-Start-VM.bat

    More information here: https://robodk.com/doc/en/Basic-Guide.html#TroubleShootIssues

KUKA C3Bridge problem

Tue, 23 Dec 2025 10:17:17 +0000

1. I am trying to run configuration script on KUKA Controller with KSS 7.1 and WinXPe 2.2 (KR5sixx R850 robot with XP). Latest RoboDK 5.9.4.
I have installed and started c3bcompt.exe on KUKA controller (v1.7.1.0).
I am able to connect to KUKA controller from RoboDK using kukabridge driver. I can also get current robot position.
However, when I try to run "KUKA Driver Auto Configuration" script, the "C3 Bridge Interface Server" on KUKA controller crush with error "The exception Privileged Instruction. (0xc0000096) occured in the aplication at location 0x00b20092"
I can not share the log, since it is not visible under the error dialog.
I have tried to connect to the robot with C3Easy (1.0.2.0), which also crush C3 Bridge interface Server.

2. I have another problem with sending program to robot controller, but I don't know if the problem
is related to previous error, since I don't know, how the program is transfered to KUKA controller.
The command "Send Program(s) to robot" from RoboDK is not working with error "Remote path not found or can't be created C:/KukaShared".
The directory exists on KRC controller and is shared (Share Permisions (everyone and target (KUKA03\target) Full Control, Security (Everyone) Full Control)
I can connect to KUKA ftp server to this directory with anonymous account.
Is there any solution to those errors?

Outdated python version in latest docker image

Fri, 28 Nov 2025 11:53:59 +0000

Program generation doesn't work in latest docker image and throws the following error

Code:
Traceback (most recent call last):

File "/home/user/RoboDK/Posts/KUKA_KRC4.py", line 39, in 

from libspp.KUKA_KRC4 import RobotPost as MainPost

ModuleNotFoundError: No module named 'libspp.KUKA_KRC4'

Upon further inspection it turns out that the `libspp` folder contains the `.so` libraries from python version 3.9 onwards but the image only has python3.8 installed. I can confirm that after installing python3.9 and updating the symlinks, things work as expected and the program is generated.

Can you update the docker image with any python version (>=3.9) that also supports loading the post processors? Thank you!

Postprocessing not working for KUKA robots

Tue, 28 Oct 2025 13:22:24 +0000

Hi, after updating to the latest RoboDK version I can't generate any program for KUKA robot, all postprocessors except KUKA_KRC1_DAT.py produces the following error.

Code:
Using Python version: sys.version_info(major=3, minor=11, micro=9, releaselevel='final', serial=0)

RoboDK Post Processor: C:\RoboDK\Posts\KUKA_KRC4.py

Using Python version: sys.version_info(major=3, minor=11, micro=9, releaselevel='final', serial=0)

RoboDK Post Processor: C:\RoboDK\Posts\KUKA_KRC2.py

Invalid Python version or post processor not found. Make sure to download the latest version of RoboDK.

Select Tools-Options-Python and select a supported Python version

This script was executed using Python 3.11.9

Information about the error:

NameError("name 'DEFAULT_HEADER' is not defined")

Traceback (most recent call last):

  File "C:\RoboDK\Posts\KUKA_KRC4.py", line 39, in 

    from libspp.KUKA_KRC4 import RobotPost as BasePost

  File "KUKA_KRC4.py", line 61, in init KUKA_KRC4

    # Set to True to include subprograms in the main program. Otherwise, programs can be generated separately.

  File "C:\RoboDK\Posts\KUKA_KRC2.py", line 56, in 

    class RobotPost(BasePost):

  File "C:\RoboDK\Posts\KUKA_KRC2.py", line 148, in RobotPost

    HEADER = DEFAULT_HEADER

             ^^^^^^^^^^^^^^

I managed to solve the problem by commenting out the following line HEADER = DEFAULT_HEADER in the KUKA_KRC2.py, but I'm not sure is it ok.

KUKA KR 270 Wrong Cartesian positions via C3 Bridge

Thu, 23 Oct 2025 09:25:08 +0000

Hi everyone,

I’m working with a KUKA KR 270 R2700 Ultra connected to RoboDK through C3 Bridge.
When I use the “Run on Robot” feature to send Cartesian moves (XYZABC), the positions received on the KUKA side are completely off — both position and orientation seem to be transformed incorrectly.

However, when I send joint targets, everything works as expected. The motion on the real robot matches the RoboDK simulation perfectly.

Here’s what I’ve checked so far:

- Tool and base frames are defined and matched between RoboDK and the KUKA controller.
- The same program runs fine when exported offline (.src/.dat) and executed directly on the robot.
- The problem only happens during online execution through C3 Bridge.

I’ve got screenshots showing:

- The RoboDK target (e.g. Target_12)
- The generated .dat file
- The actual robot setup
- The pendant showing the received E6POS values

Has anyone experienced similar behavior with C3 Bridge or Cartesian targets through RoboDK?
Is there a specific configuration step or driver setting I might be missing (e.g., base/tool sync or reference frame option)?

Any help or ideas would be really appreciated!

  kukapendent.jpg (Size: 180.15 KB / Downloads: 119)

  kukakr270.jpg (Size: 370.24 KB / Downloads: 157)

  kukaprogram.jpg (Size: 75.56 KB / Downloads: 150)

  robodksetup.jpg (Size: 223.09 KB / Downloads: 129)

RoboDK and TM cobots connection problem

Mon, 13 Oct 2025 02:43:56 +0000

Has anyone else encountered connection issues between RoboDK and TM cobots? With the newer versions of RoboDK (for example, version 5.9), I can’t connect to TM cobots properly, but with older versions (like version 5.2), everything works fine.

FAIRINO FR5 Programming Errors - Line Point and Point Table Missing

Thu, 25 Sep 2025 10:39:09 +0000

Hello everyone,
I'm a new user trying to generate programs for a FAIRINO FR5 robot using RoboDK, and I'm encountering a couple of persistent errors on the robot's software that are preventing me from running my programs.
The main errors I am seeing are:

"Line Point Error": This appears when I try to run a program with linear movements.
"Point Table Missing": The robot is telling me it can't find the point table I've defined in the program.

My process is as follows:

I have selected a curve on the object, which you can see in the station attached with this.
I generated the program for the FAIRINO CR5, post processor fairino. ( i have checked other option as well which is fairino db )
I transfer the

Code:
lua
file format to the robot controller via USB.

I've already checked the following based on my own debugging:

I have ensured that the points are reachable and not violating joint limits.

Could anyone with experience on the FAIRINO CR5 or similar controllers running on the same platform offer some insight?
Specifically, I'm wondering:

Are there any specific formatting requirements for point tables or linear moves in the FAIRINO

Code:
lua
files format that I might be missing?
Could this be a post-processor issue? Has anyone successfully used a post-processor for this specific robot model and are there any common pitfalls?
Is there a configuration setting on the robot controller itself that needs to be adjusted to properly interpret the program files?

Any guidance or shared experience would be greatly appreciated. Thank you!

  error 01.jpg (Size: 163.54 KB / Downloads: 202)

  error 02.jpg (Size: 74.99 KB / Downloads: 183)

  Polishing-new.rdk (Size: 1.47 MB / Downloads: 177)

ROKAE Post processor issues with targets

Mon, 22 Sep 2025 06:33:44 +0000

Dear RoboDK teams

When I imported the program generated by the ROKAE post-processor into the robot, an error occurred. The error is related to the way the position is described. The correct format should be as follows(note: the values shown are placeholders):

robtarget p1 = p:{{90.36818361602, 544.06466391065, 255.38181998086}, {-0.00025643758, 0.9971352969, 0.07294764017, 0.01999439197}, 0}{cfg 92, -5, -126, -3, -59, -95, 0, 0}{Ej 0,0,0,0,0,0}
Please correct this.

Also, the generated program is currently created as the main module, but please make sure to create the module using the name of the program that was created.

Accurate vs Calibrate kinematics failing to find a solution

Tue, 02 Sep 2025 20:25:05 +0000

I've ran into a few situations in RoboDK with a calibrated robot where I can solve forward kinematics, but I can't solve inverse kinematics.

Example joints where this occured:
[-12.330000, -2.750000, -36.190000, 170.420000, 0.030000, 19.520000]

For example these joint values for my calibrated Motoman mh180-120 will work forward and inverse for uncalibrated kinematics.

But if I enable calibrated kinematics forward kinematics works, but inverse fails.

I found the above joint values from a robot operating in the field that came across this error, but I was able to find many more by running the following script.

It randomly sample joint space within the robot's joint limits at whole degree values for simplicity.

I used this code for testing:

Code:
import random

limit_upper = [89.0, 75.0, 89.0, 359.0, 129.0, 359.0]

limit_lower = [-89.0, -59.0, -85.0, -359.0, -129.0, -359.0]

step = 1.0 

seed = 42

counts = [int((hi - lo) / step) for lo, hi in zip(limit_lower, limit_upper)]

if seed is not None:

    random.seed(seed)

tool = rbt.PoseTool()

frame = rbt.PoseFrame()

def random_joints(num_trials, func):

    for _ in range(num_trials):

        offsets = [random.randrange(c) for c in counts]

        jnt = [lo + off * step for lo, off in zip(limit_lower, offsets)]

        if func(jnt):

            return jnt

    return []

def test(jnt):

    rbt.setJoints(jnt)

    pose = rbt.SolveFK(rbt.Joints(), tool=tool, reference=frame)

    newjnts = rbt.SolveIK(pose, rbt.Joints(), tool=tool, reference=frame)

    if len(newjnts.tolist()) == 1:

        print(jnt)

    return False

random_joints(10000, test)