Universal Robots collaborative arms
How Tallyfy could work with Universal Robots
Section titled “How Tallyfy could work with Universal Robots”Universal Robots makes collaborative robot arms, often called cobots, and announced its newest generation in September 2026 ↗[1]. Outside software can load a program on one of these arms, start and stop it ↗[2], and read what the robot is doing.
So a robot job could be one step in a longer procedure that people run in Tallyfy. A person finishes a check, the robot runs, and someone signs off the result. Tallyfy doesn’t build or ship the link to the robot. Your developer would write it.
What Universal Robots sells today
Section titled “What Universal Robots sells today”As of October 2026, the company’s FAQ ↗[3] describes three families of arm. The number after the dash in each name is the reach in millimetres.
- e-Series, from 2018. The UR3e-540 ↗[4] carries 3 kg, the UR7e-920 ↗[5] carries 7.5 kg and the UR12e-1300 ↗[6] carries 12.5 kg.
- UR Series, from 2022. The UR20-1750 ↗[7] carries 20 kg and the UR30-1300 ↗[8] carries 30 kg.
- g-Series ↗[9], new in 2026. The UR10g-1750 carries 8 kg (10 kg extended), the UR17g-1300 carries 15 kg (17.5 kg extended) and the UR18g-950 carries 18 kg.
The FAQ also explains the names. The UR7e and UR12e were the UR5e and UR10e, and the UR20 and UR30 gained the reach in their names. Three recent arms, the UR8 Long, UR15 and UR18, are “mature” products as of October 2026. The g-Series replaced them, and they stay fully supported. The 16 kg UR16e ↗[10] is still listed too.
The g-Series arrived with a new control box, the CB7 Core ↗[11]. The FAQ says the control box decides whether a robot runs the older PolyScope 5 software or the current PolyScope X.
Universal Robots also offers UR Connect ↗[12], its own fleet service. It has a dashboard, remote access, software updates, and cloud backups of programs with version history. Approved add-ons are listed on the UR Marketplace ↗[13].
What outside software can ask a robot to do
Section titled “What outside software can ask a robot to do”Universal Robots publishes its developer interfaces. Which one you use depends on the software generation.
| What outside software does | PolyScope 5 | PolyScope X |
|---|---|---|
| Loads, starts, pauses and stops a program, and reads state | Dashboard Server ↗[14] | Robot API ↗[15], which replaced it and works only in Remote Mode |
| Streams live robot data, up to 500 times a second | RTDE ↗[16] | Same |
| Sends URScript, the robot’s programming language | Primary and secondary interfaces ↗[17], interpreter mode ↗[18] | Same |
| Answers calls from a running robot program | XML-RPC ↗[19], sockets ↗[20] | Same |
| Installs its own code on the controller | URCap written in Java ↗[21] | URCap with a web front end ↗[22] and an optional container |
PolyScope 5’s long-term support release has an end date. As of October 2026, it’s supported until the end of 2027 ↗[23], and hardware introduced after that release isn’t supported on it. The upgrade guide ↗[24], dated November 2024, says there’s no direct migration to PolyScope X: programs and settings have to be redefined, and URCaps aren’t reusable.
Two more limits apply:
- On PolyScope X, outside services start switched off, and an administrator can switch each one on or off ↗[25].
- Safety stays with the robot. Universal Robots says real-time control and certified safety remain enforced by the robot ↗[26].
Where a written procedure fits
Section titled “Where a written procedure fits”Tallyfy holds the steps people follow around the robot. A template is the written procedure, such as a changeover checklist, a first-part inspection or a weekly maintenance round. Each launch creates a process with tasks for named people, deadlines, and form fields for readings and sign-offs. Robot programs stay on the robot and in tools such as UR Connect.
Three things Tallyfy already does make a link possible:
- Another system can launch a process through the API1 and pre-fill its kick-off form.
- Tallyfy sends a webhook2 when a task is completed or a process launches.
- Every process has an activity log of who did what, and keeps the template version it launched with.
Here’s how the concept could run. An operator completes a “cell is clear” task. The webhook reaches your developer’s code, which asks the robot to load and start a stored program. When the program finishes, that code completes the next Tallyfy task through the API.
What to notice:
- The dashed boxes are your own code. Tallyfy doesn’t ship it.
- Tallyfy never talks to the robot directly.
- The robot keeps its own program and safety functions.
For developers
Section titled “For developers”(Skip this unless you’re setting up the technical side.)
A few more facts for whoever writes the code:
- ROS 2. An open-source driver ↗[27] controls an arm from an outside ROS 2 application. PolyScope X has ROS 2 built in ↗[28], and its ROS 2 documentation covers version 10.13 and later.
- Files. Program and script files can be copied to the robot over FTP, SFTP or SSH ↗[29]. A PolyScope program is a
.urpfile, which a Universal Robots staff member described in 2017 as compressed XML ↗[30]. PolyScope X can be used for offline programming from any device with a browser, and it can export a whole application as one file ↗[31]. - Factory networks. PolyScope 5 lists Modbus, PROFIsafe and EtherNet/IP ↗[32]. The CB7 Core page ↗[33] lists Modbus, EtherNet/IP, PROFINET and OPC UA.
- Port 80. From PolyScope X 10.14 it’s closed by default ↗[34], so a URCap that outside systems reach on that port needs it switched back on.
The Tallyfy side is ordinary API work. Your code can launch a process when a robot program stops, or complete a task when one finishes. Those two pages have working code samples.
Related articles
Section titled “Related articles”Robotics > KUKA industrial robots and cobots
Robotics > FANUC industrial robots and CRX cobots
Robotics > Unitree quadruped and humanoid robots