Post processors and robot drivers use different methods to move robots. While a post processor allows you to generate programs offline, a driver allows you to have real time communication with your robot.

A post processor is used for offline programming and is responsible for converting the RoboDK robot program into the native programming language of the associated robot controller. For instance, the ABB post processor generates .mod files for IRC5 controllers. The post processor also includes program uploading to the robot controller, often by FTP. The following functionalities of a program are handled by the post processor:

1.Generate Robot Program

2.Generate Robot Program as…

3.Send Program to Robot

4.Start on Robot (in combination with the driver)

Robot Programs - Image 46

A robot driver enables remote control of your robot from your computer using RoboDK. This allows you to execute program instructions from RoboDK on the robot controller in real time. This includes the ability to call remote programs on the controller. For example, the ABB driver sends motion commands through socket communication. The following functionalities are handled by the driver:

1.Activate the option Run on Robot, then double click to run the program on the robot using the driver.

2.Start on Robot (in combination with the post processor)

Robot Programs - Image 47

Note: Robot drivers send each instruction individually and wait for the controller to finish. For motion commands, it means that a small delay (apparent jerk) will occur.

Tip: In most cases, offline programming is the best way to control your robot as all the motion commands are known by the robot controller in advance (read-ahead) allowing it to take advantage of motion and speed optimization, such as rounding.

Tip: You can use a hybrid combination of the post processor and the driver, where complex paths are uploaded to the controller and called remotely by the driver. This is particularly effective when using the RoboDK API.

Post processors vs Drivers