---
title: "UR10 Collaborative Robot Arm"
space: "Factory Docs"
url: "https://factory.uga.edu/docs/equipment/ur10"
updated: "2026-11-19"
---

## Overview

The UR10 is a six-axis collaborative robot arm manufactured by Universal Robots. The lab's existing UR workcell is used for manipulation, automation, and robotics research, including pick-and-place, bin-picking, and vision-guided assembly. Current workcell expansion plans include compatible gripper tooling and a Robotiq wrist-camera system.

> **Model note:** This page describes the original 10 kg-payload, 1300 mm-reach UR10 rather than the newer UR10e or current UR10 generation. Verify the controller generation and installed PolyScope version before applying software-specific instructions.

---

## Specifications


| Parameter                 | UR10                                                                                     |
| ------------------------- | ---------------------------------------------------------------------------------------- |
| Degrees of freedom        | 6 rotating joints                                                                        |
| Maximum payload           | 10 kg / 22 lb                                                                            |
| Reach                     | 1300 mm / 51.2 in                                                                        |
| Repeatability             | ±0.1 mm                                                                                  |
| Robot weight              | 28.9 kg / 63.7 lb                                                                        |
| Base footprint            | Ø190 mm                                                                                  |
| Typical TCP speed         | 1 m/s                                                                                    |
| Base / shoulder max speed | 120°/s                                                                                   |
| Elbow / wrist max speed   | 180°/s                                                                                   |
| Robot arm protection      | IP54                                                                                     |
| Operating temperature     | 0–50 °C                                                                                  |
| Typical power consumption | \~250–350 W depending on specification revision                                          |
| Controller supply         | 100–240 VAC, 50–60 Hz                                                                    |
| Programming environment   | PolyScope                                                                                |
| Ethernet                  | 100BASE-TX                                                                               |
| Industrial communications | TCP/IP, Modbus TCP; some controller configurations also support PROFINET and EtherNet/IP |


The original UR10 provides substantially more reach than a small tabletop cobot while retaining a relatively compact base, making it useful for larger manipulation workspaces.

---

## Kinematic Structure

The UR10 is a serial manipulator with six revolute joints:

```text
Base
  |
Shoulder
  |
Elbow
  |
Wrist 1
  |
Wrist 2
  |
Wrist 3
  |
Tool / End Effector
```

The six joints provide six degrees of freedom, allowing the Tool Center Point (TCP) to be controlled in both Cartesian position and orientation.

A Cartesian tool pose can be expressed conceptually as:

```text
pose = (x, y, z, rx, ry, rz)
```

where `x`, `y`, and `z` describe position and the rotational components describe tool orientation.

---

## Major Components

A complete UR10 installation normally consists of:

- UR10 robot arm
- control box
- teach pendant
- robot-to-controller cable
- mains power connection
- end-effector tooling
- external equipment as required by the workcell

The controller executes robot programs, coordinates joint motion, manages safety functions, and provides interfaces to external automation equipment.

---

## Teach Pendant and PolyScope

The primary user interface is **PolyScope**, Universal Robots' graphical programming environment presented through the teach pendant.

PolyScope is used to:

- initialize the robot
- release the brakes
- manually move the arm
- configure the TCP
- define payload parameters
- create waypoints
- build robot programs
- configure I/O
- configure installations
- manage safety settings
- diagnose faults

A typical program is represented as a tree of commands rather than requiring the operator to write source code directly.

```text
Robot Program
|
+-- MoveJ: Home
|
+-- MoveJ: Approach
|
+-- MoveL: Pick
|   |
|   +-- Close Gripper
|
+-- MoveL: Retract
|
+-- MoveJ: Place
|   |
|   +-- Open Gripper
|
+-- MoveJ: Home
```

---

## Coordinate Frames

Understanding coordinate frames is fundamental to programming the UR10.

### Base frame

The **Base** frame is fixed relative to the robot mounting surface.

### Tool frame

The **Tool** frame is attached to the active Tool Center Point.

### TCP

The **Tool Center Point (TCP)** defines the useful working point of the installed end effector.

For a gripper, the TCP is normally near the grasping point rather than at the mechanical tool flange.

Incorrect TCP configuration causes apparently correct Cartesian movements to behave incorrectly when the tool rotates.

### Feature frames

User-defined features can represent objects such as:

- tables
- fixtures
- conveyor belts
- workpieces
- assembly stations

Programming relative to a meaningful feature is generally preferable to encoding every waypoint directly in the robot's Base coordinate system.

---

## Motion Commands

Two fundamental UR motion types are joint-space and Cartesian linear motion.

### MoveJ

`MoveJ` generates a trajectory primarily in **joint space**.

Use it when:

- the exact Cartesian path is unimportant
- moving between distant poses
- fast general repositioning is desired

The tool does **not** necessarily travel along a straight line between positions.

### MoveL

`MoveL` generates a **linear Cartesian trajectory** for the TCP.

Use it when:

- approaching a workpiece
- inserting or extracting a tool
- maintaining a predictable Cartesian path
- performing process operations where tool path matters

### Practical sequence

A common manipulation pattern is:

```text
MoveJ -> Approach pose
MoveL -> Pick pose
        Grasp
MoveL -> Approach pose
MoveJ -> Destination approach
MoveL -> Place pose
        Release
MoveL -> Destination approach
```

This combines efficient joint-space transit with controlled Cartesian movement near objects and fixtures.

---

## Waypoints

A waypoint defines a target robot configuration or TCP pose within a program.

Common waypoint types include:

- fixed waypoints
- relative waypoints
- variable waypoints

When teaching waypoints, consider both the desired TCP pose and the resulting robot joint configuration. Multiple joint configurations can produce similar TCP poses, but some configurations may be close to joint limits, obstacles, or singularities.

---

## Freedrive

Freedrive allows an operator to physically guide the robot arm by hand while the controller compensates for the robot's weight.

It is useful for:

- teaching waypoints
- demonstrating motions
- approximate positioning
- quickly developing manipulation tasks

Freedrive should not be confused with the safety system. A robot that is easy to physically guide can still create crushing, trapping, impact, or tooling hazards depending on the application.

---

## Payload and Center of Gravity

The controller must be configured with the mass and center of gravity of the installed payload.

The effective payload includes components carried by the robot, such as:

```text
Payload = End Effector + Adapter + Workpiece + Attached Accessories
```

For example, if the installed tooling consists of:

```text
Gripper        1.0 kg
Camera         0.4 kg
Adapter        0.3 kg
Workpiece      2.0 kg
--------------------
Total          3.7 kg
```

then the robot should be configured for the appropriate mass and center of gravity of the complete 3.7 kg assembly.

Incorrect payload configuration can degrade:

- trajectory performance
- force estimation
- collision detection
- stopping behavior
- joint control

Payload capacity also depends on the center-of-gravity offset and robot configuration, not merely the nominal mass limit.

---

## End Effectors and Vision

The lab's UR10 workcell is being expanded with gripper and vision hardware for applications including:

- pick-and-place
- bin picking
- object localization
- vision-guided grasping
- assembly
- manipulation research

A Robotiq wrist-camera system can provide in-hand vision near the end effector, making the camera pose move with the robot rather than remaining fixed in the workcell.

A typical vision-guided manipulation pipeline is:

```text
Camera
  |
  v
Image Acquisition
  |
  v
Object Detection / Pose Estimation
  |
  v
Camera-to-Robot Transform
  |
  v
Target TCP Pose
  |
  v
Motion Planning / Robot Program
  |
  v
UR10 + Gripper
```

Reliable vision-guided manipulation requires a known transformation between camera coordinates and robot coordinates.

---

## I/O

The original UR10 control box provides digital and analog I/O for workcell integration.

Typical controller resources include:

- 16 digital inputs
- 16 digital outputs
- 2 analog inputs
- 2 analog outputs
- 24 V I/O supply

The tool connector also provides local I/O at the wrist for compatible end effectors and sensors.

Typical uses include:

- opening and closing a gripper
- reading a part-present sensor
- triggering a camera
- communicating readiness to a PLC
- controlling pneumatic valves
- coordinating with conveyors or other machines

---

## Network Integration

The UR10 controller exposes Ethernet connectivity and can participate in larger automation or research systems.

```text
+--------------------+
| Research Computer  |
| / PLC / Controller |
+---------+----------+
          |
       Ethernet
          |
          v
+---------+----------+
| UR10 Control Box   |
+---------+----------+
          |
          v
+--------------------+
|     UR10 Arm       |
+--------------------+
```

Depending on controller generation, installed software, and application, useful interfaces can include:

- TCP/IP socket communication
- Modbus TCP
- PROFINET
- EtherNet/IP
- URScript
- Dashboard Server
- Real-Time Data Exchange (RTDE)

Check compatibility against the actual controller and PolyScope version before designing an interface around a particular protocol.

---

## URScript

URScript is Universal Robots' robot programming language. It provides lower-level programmatic control than the PolyScope graphical program tree.

Conceptually:

```python
movej(joint_target, a=1.0, v=1.0)
movel(target_pose, a=0.5, v=0.2)
set_digital_out(0, True)
sleep(0.5)
```

URScript can be used for:

- robot motion
- I/O control
- variables and logic
- socket communication
- functions
- integration with external control software

Do not treat network access to URScript as a substitute for the robot's safety system. An external application issuing robot commands must still operate within a properly configured and risk-assessed workcell.

---

## Safety

The UR10 includes configurable safety functions intended to support collaborative and conventional industrial applications.

The original UR10 safety system was tested to standards including **EN ISO 13849-1 PL d** and **EN ISO 10218-1**.

Collaborative capability does **not** automatically make an application safe without guarding.

The complete application must account for hazards introduced by:

- the workpiece
- gripper fingers
- sharp tooling
- cameras and brackets
- fixtures
- tables and walls
- robot speed
- robot payload
- crushing or trapping locations
- other machines in the workcell

A blunt collaborative arm carrying a sharp tool is still a sharp-tool robot.

### Before operation

- Verify the correct installation and safety configuration.
- Verify the Emergency Stop circuit.
- Confirm payload and center-of-gravity settings.
- Check that the selected TCP matches the installed end effector.
- Inspect tooling and mounting hardware.
- Keep the workspace clear while testing new programs.
- Run new motions at reduced speed before full-speed operation.
- Check paths for crushing and pinch hazards, not only endpoint collisions.

Changes to tooling, payload, fixtures, safety limits, or the physical workcell can change the risk assessment.

---

## Singularities

Like other six-axis serial manipulators, the UR10 can encounter kinematic singularities.

Near a singularity, a relatively small requested TCP motion can require very large joint velocities or cause the robot to select an undesirable joint configuration.

Symptoms can include:

- unexpectedly slow motion
- protective stops
- sudden changes in wrist configuration
- inability to execute a desired Cartesian trajectory

When troubleshooting motion problems, distinguish between:

1. an unreachable Cartesian target,
2. a joint-limit problem,
3. a collision or safety limit,
4. a singular configuration,
5. a poorly selected waypoint or TCP.

Changing an approach orientation or intermediate waypoint can often produce a better-conditioned trajectory.

---

## Collision and Reachability Considerations

A target TCP pose being inside the nominal 1300 mm reach does not guarantee that it is practically reachable.

Reachability also depends on:

- TCP orientation
- tool length
- joint limits
- configured safety limits
- nearby obstacles
- self-collision constraints
- desired approach path

Design workcells around **usable dexterous workspace**, not simply the arm's maximum reach radius.

---

## Troubleshooting

### Robot cannot be initialized

Check:

1. Emergency Stop state.
2. Safety faults.
3. Control-box status.
4. Robot power state.
5. Communication between the controller and arm.
6. Active messages in PolyScope.

### Robot reports a protective stop

Do not simply reset repeated protective stops.

Check:

- collisions or contacts
- incorrect payload configuration
- aggressive acceleration
- singularities
- constrained tooling
- external forces
- safety-plane or safety-limit violations

Repeated protective stops are usually evidence of an underlying configuration, trajectory, mechanical, or process problem.

### Tool does not move as expected

Verify:

- active TCP
- payload settings
- feature frame
- waypoint type
- MoveJ versus MoveL selection
- orientation representation

### External computer cannot communicate with robot

Check:

- robot IP address
- subnet configuration
- Ethernet link
- selected service or protocol
- firewall rules
- required PolyScope settings
- controller generation and software compatibility

Test basic IP connectivity before debugging the application protocol.

---

## Research Use

The UR10 is a useful research platform for:

- manipulation
- visual servoing
- grasp planning
- machine tending
- human-robot collaboration
- learning from demonstration
- AI-based object recognition
- robotic assembly
- force-aware manipulation
- manufacturing automation

For experimental systems, a useful architectural boundary is:

```text
Perception / AI / Planning
          |
          v
High-Level Robot Command
          |
          v
UR Controller
          |
          v
Trajectory + Safety Enforcement
          |
          v
UR10 Arm
```

Keeping experimental perception and planning software separated from the robot's safety functions makes the system easier to reason about, test, and recover when research software fails.

---

## References

- Universal Robots, *UR10 Technical Specifications*, Item No. 110110.
- Universal Robots, UR10/CB-series documentation and PolyScope manuals applicable to the installed controller revision.
- ISO 10218-1, *Robotics — Safety requirements — Part 1: Industrial robots*.
- ISO 13849-1, *Safety of machinery — Safety-related parts of control systems*.