URCAP MARKETPLACE
All URCaps

MIGRATION · POLYSCOPE 5 → POLYSCOPE X

Move PolyScope 5 programs to PolyScope X – without rebuilding everything by hand

Universal Robots currently offers no direct migration from PolyScope 5 to PolyScope X – programs and settings would have to be redefined. URP Import X closes that gap: the .urp file is read on the robot together with its .installation and .variables and rebuilt as native PolyScope X program nodes. Anything without a counterpart is flagged and listed in the migration report.

.urp → PolyScope XInstallation & variables includedMigration reportTested on e-Series & UR Gen7

“There is no direct software migration from Polyscope 5 to Polyscope X currently. All settings and programs will need to be redefined.”

Source: Universal Robots: Upgrading From a Polyscope 5 Controller to a Polyscope X Controller

HOW IT WORKS

From a .urp program to a PolyScope X program in five steps

  1. Select files on the robot

    Pick the program (.urp), installation and variables straight from a USB stick on the robot – gzip-compressed or plain XML. Subprograms from additional .urp files are included.

  2. Pre-check

    Missing TCPs, frames, signals and variables are shown before anything is inserted.

  3. Dry run

    The target tree is built in memory and the coverage is shown – without changing the program.

  4. Import into its own folder

    The program is created as native nodes in a dedicated folder so imports never mix. Built waypoints are verified against the source file.

  5. Review the migration report

    Every source node and its result is listed in the report, which is also written to the USB stick next to the source program. Imports can be undone node by node.

IN DETAIL

What URP Import X transfers

Moves & positions

MoveJ, MoveL, MoveP and MoveC as native move nodes; positions computed from joint angles when the source stores no pose; waypoint names are kept, relative waypoints are transferred with the offset shown.

Program logic

If, Else If, Else, Loop, Folder and Threads. Switch/Case becomes an If chain because PolyScope X switches on variables.

Signals & I/O

Digital, analog and configurable inputs and outputs including the tool connector. Signal names are resolved from the installation, e.g. “GripperOpen” to “DO 2”.

Installation & variables

TCPs, payload, features and signal names from the .installation; program variables and installation variables as application variables – with their values.

Operator input & special cases

Operator inputs, Safe Home moves, directional moves with stop conditions. URScript lines are checked and simple errors repaired.

Third-party URCaps

Unknown constructs are catalogued. Custom conversion rules for other URCaps’ nodes can be stored, exported as JSON and reused on other robots.

FROM THE FIELD TEST

URP Import X on a UR17g-1300

PolyScope 5 program imported into PolyScope X with URP Import X: imported folder with moves, operator input, wait, script and if conditions in the program tree of a UR17g-1300
An imported program in the PolyScope X program tree: the import sits in its own folder.
URP Import X in the PolyScope X application area on the TP7 Core of a UR17g-1300 (UR Gen7)
URP Import X appears directly in the PolyScope X application area.
URP Import X – screenshot 1 in PolyScope X
URP Import X in PolyScope X – screenshot 1
URP Import X – screenshot 2 in PolyScope X
URP Import X in PolyScope X – screenshot 2

CONTROL & LIMITS

Nothing is hidden

Not every PolyScope 5 node has a direct counterpart in PolyScope X. URP Import X flags those places in the program and lists them in the migration report instead of silently dropping them. Review the imported program like any new program and test it at reduced speed first.

READ NEXT

Related

URCap · PolyScope XURP Import XPolyScope-5-Programme (.urp) samt Installation in PolyScope X übernehmen: Bewegungen, Logik, Signale und Variablen als native Programmknoten – mit Migrationsbericht.TopicProgram Universal Robots with AI – from a prompt, directly in PolyScope XProgram your cobot with AI: type a prompt on the teach pendant and the AI builds native PolyScope X program nodes – with ChatGPT/Codex, OpenAI or Claude.PlatformURCaps for UR Gen7Tested live on a UR17g-1300 with PolyScope X.

QUICK ANSWERS

Frequently asked questions

Can PolyScope X open PolyScope 5 programs?

Not directly. According to Universal Robots there is currently no direct software migration from PolyScope 5 to PolyScope X. URP Import X reads .urp files and rebuilds them as native PolyScope X program nodes.

Is the installation transferred as well?

Yes. TCPs, payload, features and signal names from the .installation as well as installation variables from the .variables file are transferred.

What happens to nodes without a PolyScope X counterpart?

They are flagged at the right place in the program and listed in the migration report. Custom conversion rules can be stored for other URCaps’ nodes.

Can I undo an import?

Yes. Every import sits in its own folder and can be undone node by node without touching other changes.

Do I need a PC?

No. Files are selected on the robot from a USB stick, and the migration report is written back to the stick.

Does it work for UR Gen7?

Yes. UR Gen7 runs PolyScope X only. URP Import X was tested on the e-Series with PolyScope X and live on a UR17g-1300.

NEXT STEP

Take your PolyScope 5 programs with you

Briefly describe how many programs need to move and which URCaps they use. You will get an assessment of the expected coverage and an offer for URP Import X.

URP Import X – request