Skip to content

Uploading programs

Jump to bottom
visose edited this page Jun 28, 2026 · 1 revision

Robots can save generated robot code to disk. Some manufacturers also support network upload or execution through the Remote Connection component.

Always review generated code and validate it on the controller before running the robot. Start at reduced speed and follow the normal safety procedure for the cell. Remote upload is a convenience feature, not a replacement for controller-side review.

Save program

Use Save Program to write the generated code to a folder. If Create Program reports errors, code is not generated and there is nothing safe to save.

After saving, transfer the files to the controller using the normal method for that robot brand: USB drive, controller file share, FTP/SFTP, vendor software, or the Robots remote component where supported.

If you manually edit generated code after saving, Robots can no longer check or simulate those edits.

Before transferring code, review:

  • Create Program errors and warnings.
  • Tool and frame names or controller numbers.
  • IO names or numbers.
  • Program and file names.
  • Speed and zone values for first physical tests.
  • Manufacturer-specific limitations in Manufacturer support.

Remote Connection component

The Remote Connection component accepts a Program, optional IP, and boolean inputs for Upload, Play, and Pause.

Remote support currently exists for:

  • ABB
  • UR
  • Franka Emika

Other manufacturers should use Save Program and the controller's normal file-transfer workflow.

If remote upload fails, start with the component Log output, then see Troubleshooting.

ABB

ABB remote upload is available on Windows. It uses an ABB helper process and requires the ABB communication runtime available through RobotStudio or ABB Robot Communication Runtime.

If no IP address is supplied, Robots asks the ABB helper to use the first discovered controller. Supplying the controller IP is usually clearer when more than one controller is visible on the network.

ABB remote upload currently supports one RAPID task, T_ROB1.

UR

UR remote support has two modes:

  • 192.168.0.10: streams the program through the secondary client interface and supports play/pause commands.
  • sftp://192.168.0.10: uploads a .urp file through SFTP and loads it through the dashboard interface.

The SFTP URL can include a username and target path, for example sftp://user@192.168.0.10/programs. Avoid storing passwords in shared Grasshopper definitions.

For long programs or repeatable production setup, saving the program and transferring it through the controller's normal workflow can be easier to audit.

Franka Emika

Franka Emika remote support uploads generated Python code to the controller over the network and can start or pause the uploaded program. Use the component log to confirm upload and execution state.

Manual transfer notes

  • KUKA: KUKA controllers commonly expose Windows file shares. Save the KRL program, copy it to the controller, and load it from the pendant.
  • ABB: RobotStudio can transfer saved RAPID modules to the controller if the remote component is not used.
  • UR: programs can be transferred through SFTP or other controller-supported workflows.
  • Staubli, Doosan, Fanuc, Igus, Jaka: save the generated files and use the controller or vendor workflow expected for that controller.

Controller setup, permissions, safety modes, and program folder paths vary by installation. Treat the generated files as source material that still needs controller-side validation.

Clone this wiki locally