The RoboDK API documentation is available here. Some examples that use the Python API are available here.
Reference frames allow placing objects with respect to each other. Drag & drop any reference frame or object in the Station Tree to create nested reference frames.
Hold the Alt key to move Reference Frames by selecting them on the 3D view. It is also possible to manually enter the translation and rotation values specific to any robot, including quaternion values and different types of Euler rotations. Select the preferred Euler orientation in the menu: Tools-Options-General-Default Euler Angles mode.
Select the buttons on the right to copy/paste the values from/to an array of values or as a 4x4 pose.
Alt | Move reference frames, robots or other objects | |
Alt+Shift | Move robot TCP (tools) | |
Ctrl+0 | Fit the 3D view to the selected object(s) | |
F1 | Shows the RoboDK documentation | |
F2 | Rename item | |
F6 | Generate program(s) | |
F7 | Show/hide selected object(s) | |
+ | Make frames bigger | |
- | Make frames smaller | |
/ | Show/hide text | |
* | Show/hide robot workspace | |
Ctrl + 1 | Load last file or RoboDK Station |
Double click a robot to open the robot panel and jog the robot axis by axis or in the Cartesian space. The robot tool (TCP) and Reference frames can be modified in this window.
Double click a program to view the simulation.
Learn more about simulation and offline programming in the documentation
Robot tools can be easily created by importing a 3D object and drag & dropping it to the robot. The object is then automatically converted into a tool. Import 3D objects to model the cell. Accepted 3D formats include STL, IGES and STEP files.
Learn more about creating robot tools in the documentation
Once a simulation is ready, export it as a 3D HTML simulation or as a 3D PDF. This feature allows to easily sharing layout and simulation concepts.
Example of a 3D HTML simulation document
Example of a 3D PDF simulation document (3D PDF simulations must be opened with Acrobat Reader, not a browser)
Tip: HTML simulations are larger than PDF simulations, compressing them will considerably reduce their size. The HTML simulation does not have any dependencies and can be shared as one single file.
The robot Post Processor defines how the robot programs should be generated. The conversion of the simulator movements to specific robot instructions is done by a Post Processor. Post Processors provide complete flexibility to generate the robot programs for specific requirements.
RoboDK provides Post Processors for most robot brands. Post Processors can be easily created or modified. One Post Processor in RoboDK is simply a Python file that defines how the code should be generated. Each robot brand uses a default post processor that can be modified to customize program generation and better adjust to specific applications.
Tip: Double click a post processor to see a preview of a sample robot program.