RoboDK provides over 100 post processors by default to support generating robot programs for over 40 robot manufacturers. Some post processors can be further customized to generate programs with a specific format.

You can find the complete list of available post processors in the RoboDK Library by navigating to https://robodk.com/posts. You can also select Tools➔Open Robot Library from the main toolbar in RoboDK.

By default, the following post processors are available in RoboDK:

● ABB RAPID IRC5: for ABB IRC5 robot controllers

● ABB RAPID S4C: for ABB S4C robot controllers

● Adept Vplus: for Adept V+ programming language

● Allen Bradley Logix5000: for Allen Bradley Logix5000 PLC

● Aubo: for AUBO robot controllers

● Brooks: for PreciseFlex robots

● CLOOS: for CLOOS robot controllers

● Comau C5G: for Comau C5G robot controllers

● Denso PAC: for Denso RC7 (and older) robot controllers (PAC programming language)

● Denso RC8: for Denso RC8 (and newer) robot controllers (PacScript programming language)

● Dobot: for educational Dobot robots

● Doosan: for Doosan collaborative robots

● Epson: for Epson robot controllers

● Fanuc R30iA: for Fanuc R30iA and R30iB robot controllers

● Fanuc R30iA_Arc: for Fanuc Arc welding

● Fanuc RJ3: for Fanuc RJ3 robot controllers

● GCode BnR: for B&R robot controllers

● GSK: for GSK robots

● HCR: for Hanwha robot controllers

● HIWIN HRSS: for HIWIN robots

● Hyundai: for Hyundai robot controllers

● KAIRO: for Keba Kairo robot controllers

● Kinova: for Kinova robots

● Kawasaki: for Kawasaki AS robot controllers

● KUKA IIWA: for KUKA IIWA sunrise programming in Java

● KUKA KRC2: for KUKA KRC2 robot controllers

● KUKA KRC2_CamRob: for KUKA CamRob milling option

● KUKA KRC2_DAT: for KUKA KRC2 robot controllers including DAT data files

● KUKA KRC4: for KUKA KRC4 robot controllers

● KUKA KRC4_Config: for KUKA KRC4 robot controllers with configuration data in each line

● KUKA KRC4_DAT: for KUKA KRC4 robot controllers including DAT data files

● Mecademic: for Mecademic’s script code required by the Meca500 robot

● Mecademic Python: it generates a Python script that can control the Mecademic Meca500 robot remotely.

● Mitsubishi: for Mitsubishi robot controllers

● Motoman/Yaskawa: for different Motoman robot controllers using Inform II and Inform III (JBI)

● Nachi AX FD: for Nachi AX and FD robot controllers

● Omron: for Omron/Techman robot controllers

● OTC: for Daihen OTC robot controllers

● Panasonic: For Panasonic PRG programs (requires Panasonic G2PC tools to compile ASCII files to binary files)

● Robostar: for Robostar robot controllers

● Siasun: for Siasun robot controllers

● Siemens_Sinumerik: for Siemens Sinumerik ROBX robot controller

● Staubli VAL3: to generate Staubli VAL3 robot programs (CS8 controllers and later). It inlines the robot movements.

● Staubli VAL3_Machining: for Staubli VAL3 controllers that have the Machining HSM option.

● Staubli S6: for Staubli S6 robot controllers

● Toshiba: for Toshiba robots

● Techman: for Omron/Techman robot controllers

● Universal Robots: for UR robots, it generates linear movements as pose targets

● Universal Robots URP: for UR robots, it generates a URP that can be loaded and modified in Polyscope (the UR robot controller)

● Universal Robots_RobotiQ: for UR robots including support for RobotiQ gripper

● Universal Robots_MoveP: for UR robots, it generates linear movements as MoveP commands

● Yamaha: for Yamaha robots

Note: Some robot controllers, such as Fanuc and Panasonic controllers, require specific software or controller options provided by the manufacturer to support loading the program files generated by RoboDK. For example, Panasonic robots require G2PC tools to convert the program file generated by RoboDK to a binary file that can be read by the controller. Some Fanuc robots support ASCII files generated by RoboDK, alternatively, you can compile programs using Roboguide’s maketp utiliy. Learn more in the LS to TP Fanuc compilation section.

Note: The list and behavior of the default RoboDK post processors changes from time to time. This means that the generated code using the same post processor may be different with different versions of RoboDK. To prevent unexpected changes of your generated code you should make sure to create a unique copy or customize your post processors so that your generated code does not change when you update or reinstall RoboDK.

Available Post Processors