Posts by Jeremy RoboDK

    Hi Massula,

    I took a look at your file.

    First, I never saw anyone with a station split like this one.

    It was really 759 different little stl files. Very surprising.

    You have 2 options here:

    1 - If you want to keep them separated:

    a. Import the files.

    b. Create a reference frame.

    c. Select all the files (Select the first one -> Shift + select the last one).

    d. Right click -> "Change support" -> "Frame 1"

    e. Rotate the frame in the wanted orientation, all the parts should now follow it.

    2 - I you want them merges:

    a. Import the files.

    b. Remove the unwanted files.

    c. Merge the files.

    d. Modify the orientation of the merged file.

    The fact that it "shatter" if you do "split object" is normal, it's splitting the object into its "triangles" (which means a whole lot of triangles in your case).

    Hope it helps.

    Hi there,

    Importing "hand-written" program is not an officially supported feature.

    Therefore, we cannot guarantee any result.

    I still recommend you to give it a try.

    Start by building your station with the same robot and tool(s) as in your program.
    You can then drag and drop the program in RoboDK's window.

    If things turn out well, you can retrieve the movements and the target.
    If only the movements appear, select the movements (one or many at the same time) -> "right click" -> "Select Targets".

    If you are importing from KUKA, we also have a dedicated script to import .src files.

    "Main menu" -> "Tools" -> "Run Script" -> "Import_KUKA_SRC_Program"

    Hope it helps.

    Have a great day.


    Hi Lasse,

    You can go on our YouTube channel (just look for RoboDK), I created a video explaining how to use the milling features of Fusion with RoboDK.

    Hope it helps.


    Hi there,

    If you use Fusion 360 to create your machining path, you can use RoboDK's plugin to automatically transfer the part and the program from one software to the other. It will automatically create a machining project in RoboDK.

    If you use any other CAM software, you can simply drag and drop a GCode file (.gcode, .nc, .apt, etc.) in RoboDK to create a machining project.

    Once the Machining project is created with the machining program, you can adjust settings like tool orientation and spindle activation.

    You can drive the Kuka robot directly from RoboDK. If you choose that path, RoboDK will stream the movement command one by one to the robot controller.
    Considering the general size of a machining project, another option would be to simply generate the .src file (Kuka program) from RoboDK and copy it to your robot controller.

    Have a great day.


    Hi Joan,

    I just answer your email.
    But I feel the need to clarify some things.

    RoboDK, as many other robots agnostic simulator and offline programming software, does not simulate the behavior of the robot controller as a whole.
    It only simulates the movements of the robot according to the mathematical model of the robot in the controller.
    We are not equipped with a "virtual controller".

    On the offline programming side, our goal is to generate the code linked with a challenging path.
    We can output code for any of the robot brands we support (ex Kuka, ABB, Fanuc, UR, Yaskawa, etc).

    You can think of challenging paths like welding, glue dispensing, remote TCP, machining, deburring, painting, etc.

    In other words, RoboDK can generate the code for the robot controller, it can even use some controller specific function, but it's not meant to go from the real controller to RoboDK.

    For some robot brands, you can import hand written programs (ex KUKA) but the only thing you will really get out of it are the move commands and the position.

    On the simulation side, you can create pretty much any robotic process involving robot. It can be used for reach study, cycle time study or as a selling tool.

    I hope it helps clarify things.

    Hi guys,

    If you want, write me a private message with your email address and I can send you a free 30-day license of RoboDK.
    You can then try and see if it fits your needs as a brand agnostic robot simulator and offline programming software. I can also send you some training material so that you can be up and running as fast as possible.

    Have a great day.


    Hi there,

    These programs need to be created by the integrator (you in this situation).
    For example, the CALL SETTOOL1, you should create a subprogram that will go to your tool changer (if you have more then one tool) and pick Tool #1.

    For the CALL SETRPM, it should come with a parameter, this parameter represents the RPM of the spindle at a given time. So your SETRPM program should set the RPM of your spindle according to that parameter.
    The value of the RPM comes directly from the gcode (.gcode, .nc, .apt) file that you used to generate the machining path.

    Have a great day.


    Hi there,

    Just a little correction here.


    For creating off-line programs that can be exported directly to a robot, I'm pretty sure you need the paid version.

    The free version allows pretty much the same features as the paid version. You can create advanced, offline path with the free version. The only limitation is the number of lines you can output to your robot controller.
    Obviously we want people to be able to try our software and see its power before buying, but we don't want them to just put the free version on a VM and reset the free license every day. Hehe.

    Hi guys,

    You can find all the info to connect RoboDK with a KUKA controller and stream the program by following this link to our online documentation.

    If some of you are interested in testing a fully unlock version of RoboDK for a month or so, just send me a private message with your email address, I'll send you a fully unlock trial license. (The free version available on our web site has some limitation, especially when it comes the time to export the program to the robot controller.)

    Have a great day.


    Hi there,

    This is not a standard feature of RoboDK, but if you really need it, I think the best way would be to create a new robot starting with the 3D model of it and our "Model mechanisms and robots" feature.

    This way, you will be able to add your dresspack to the part of the robot it's supposed to be attached before creating the robot inside RDK.

    It the 3D model of the robot is available, it shouldn't be too hard/long to achieve.

    This YouTube video will help you with that :

    External Content
    Content embedded from external sources will not be displayed without your consent.
    Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.

    Hope it helps.
    Have a great day.


    Hi David,

    Simply put, you need to show the RoboDK where are, in real life, the frame you created.

    If you connected your robot to RoboDK, yon can use the ''Utilities -> Define Reference Frame (User frame)'' option. (See attachment)

    I recommend you to use the "3 points (p3 crosses Y+)" method. Once the robot is connected to RoboDK, you can bring it manually (using the teach) at every point (P1 to P3) and click on "Get p#" to pull the current position of the robot from the controller.

    You can follow this link to RoboDK's doc :

    The reference frame in RDK will then be adjusted to fit the reality.

    Hope it helps.


    Hi there,

    You did a good job with only 1.5 days of work.

    Here's for the simulation speed.

    By default, RoboDK simulates 5x times faster than the supposed to be real time by default. This setting can be changed in:
    Also, be sure that you are not fast forwarding the simulation (you can toggle the ''play'' or ''fast forward'' button to do so).

    Also, some parameters need to be considered to accurately calculate cycle time in RoboDK. It is important to note that the real acceleration will highly depend on the robot payload and position of the robot, therefore, the cycle time will be an estimate. More information here:

    You need to make sure you have a Set Speed instruction imposing all joint and linear speeds and accelerations. This makes sure that the speeds and accelerations are properly set in the program. You can set/change the speed in a program using Program->Set Speed Instruction:

    Another detail:
    RoboDK assumes that the robot does point to point movements (stopping at each point). So it has a uniform acceleration up to it reaches the maximum speed, then, uniform deceleration.
    This behavior can be changed on the real robot from RoboDK if you use Program-Set Rounding instruction:
    This instruction allows the robot to maintain a more constant speed while rounding the edges of the path, so the time will be faster on the real robot. On the other hand, RoboDK does not take this behavior into effect for cycle time calculation.

    It would be nice if you could send us the RoboDK station that you created. One day, we could create a demo from it and add it to the library.
    You can create a thread here :
    If you have any other question, feel free to ask, here or on our forum. (We can be faster at answering in our forum since we monitor it every day.)

    Have a good day.

Advertising from our partners