How fast is robot setup with Aurevix?

Typically hours, not weeks — for a first task from initial recording to robot running. Traditional setup with a specialist engineer takes 3–5 weeks.

Do I need a robotics engineer to use Aurevix?

No. Any factory worker can set up a robot task. If they can demonstrate a task and describe it out loud, they can use Aurevix. No robotics knowledge, no coding, no special training required.

Which robots does Aurevix support today?

Universal Robots (UR3, UR5, UR10, UR16, UR20) and ABB (GoFa, SWIFTI) are available today. FANUC, KUKA, Techman, and Yaskawa are on the near-term roadmap.

What does Aurevix cost?

Flexible subscription pricing with no per-task fees and no integrator invoices. We offer Starter, Professional, and Integrator tiers — talk to us for specifics.

Can Aurevix handle multi-step tasks?

Yes. You can chain pick, orient, place, and machine-tend into a single program with conditional branches and signal-waits between steps. Multi-step sequencing is a core capability.

What gripper types does Aurevix support?

Aurevix supports pneumatic, electric, and vacuum grippers. Pneumatic grippers make up 55–60% of installed industrial grippers, so we build for the hardware most factories already have.

How does Aurevix understand what I am demonstrating?

Aurevix uses vision-language-action (VLA) models — the same technology behind Google RT-2 and OpenVLA — to interpret your phone video and voice narration, translating them into precise robot motion sequences.

Yes. All data is processed in isolated containers with zero persistence. Enterprise customers can deploy on-premise. Aurevix is GDPR compliant and SOC 2 ready.

Can I program a robot without a teach pendant?

Yes. Aurevix replaces the teach pendant with a phone camera and voice. Workers demonstrate the task naturally and Aurevix converts it into robot motion automatically — no specialist training.

Does Aurevix support FANUC robots?

FANUC robot integration is on our near-term roadmap. Currently Aurevix supports Universal Robots and ABB cobots. Join the waitlist at agenticconvergent.com to be notified when FANUC support launches.

Universal Robots Programming Without Code: What Is Actually Possible Today

Universal Robots makes the most widely deployed collaborative robot arms in the world. The UR5e and UR10e appear in tens of thousands of factories across automotive, electronics, food processing, logistics, and machine tending applications.

Yet despite UR's reputation for being "easy to deploy," most small manufacturers still call an integrator every time they want to set up or change a task. The hardware is approachable. The programming layer is not.

This article explains why, what no-code approaches can realistically deliver today, and what tasks are genuinely within reach without a specialist.

Why Traditional UR Programming Is a Barrier

Universal Robots provide two programming interfaces:

PolyScope — the graphical user interface on the teach pendant. It uses a node-based program structure where each step is a node (MoveJ, MoveL, WaitForSignal, etc.) with configurable parameters. Non-specialists can navigate PolyScope for simple tasks, but complex programs with conditional logic, loops, and signal handling quickly require training to avoid errors.

URScript — the underlying programming language, similar to Python, that compiles to robot motion commands. Flexible and powerful; requires genuine programming knowledge to use effectively for non-trivial tasks.

Both interfaces require:

Knowledge of the robot coordinate system and motion types (joint vs. linear vs. process moves)
Understanding of the robot's digital I/O configuration
Ability to configure force control parameters (for contact tasks)
Knowledge of UR's safety system and speed/force limits

For a qualified robotics engineer, this is straightforward. For a factory worker or production manager without that background, it is genuinely difficult — and mistakes can result in collisions, wasted material, or unsafe robot behaviour.

What PolyScope Has Improved

Universal Robots has invested in making PolyScope more accessible. PolyScope X (introduced with the new e-Series) includes:

An improved touch-screen interface
Better visual feedback on waypoint positions
Easier I/O configuration with named signal labels
Improved simulation in the pendant UI itself

These improvements make PolyScope more accessible than it was five years ago. Simple pick-and-place tasks can be configured by a trained but non-specialist worker in a few hours — if that worker has had training on UR-specific pendant use.

The limit: training takes time and some technical aptitude. And for each new UR-specific feature or complex task, knowledge requirements grow.

What URCaps Are and When They Help

URCaps are software plugins that integrate external hardware (grippers, sensors, vision systems) directly into PolyScope. A URCap from Robotiq, for example, adds a gripper control node to PolyScope that lets workers configure grip force and position from a UI, without writing URScript.

URCaps lower the barrier for specific hardware integrations. But they:

Require installation and configuration on the UR controller
Vary in UI quality across vendors
Do not help with the task structure itself — just the specific hardware control

For manufacturers using off-the-shelf grippers with good URCap support (Robotiq, Schunk, OnRobot), URCaps are worth using. For custom hardware or pneumatic grippers, URCap support may be limited.

What Demo-Based No-Code Platforms Actually Do

A different class of programming tool removes PolyScope from the setup workflow entirely. Instead of navigating a pendant UI, a worker:

Records a video demonstration of the task using a phone camera
Narrates what they are doing in plain language
Reviews the AI-generated program in a 3D simulation
Deploys to the UR robot via a single click

The output is a valid URScript program (or equivalent) that runs directly on the robot. The worker never opens PolyScope.

What this means practically:

No pendant training required
No URScript knowledge required
Task changes follow the same workflow — demonstrate, review, deploy
Changeover measured in hours, not weeks

What it requires:

A compatible robot (UR3, UR5, UR10, UR16, UR20 — specific version compatibility varies by platform)
A network connection to the robot controller
A gripper type supported by the platform
A task within the platform's capability envelope (pick-place, machine tending, assembly sequences with standard grippers)

What Is Actually Possible Today

To be specific and honest, here is what is within reach for a small manufacturer with a Universal Robots cobot in 2026, without specialist involvement:

Genuinely doable:

Pick-and-place tasks with uniform parts (conveyor to bin, bin to fixture)
Machine tending sequences with standard UR signal I/O (load part, cycle wait, unload)
Simple assembly tasks (insert pin, place cover, route connector)
Quality checking with vision (presence/absence, orientation)

Possible but with more effort:

Multi-station transfer tasks (multiple pick and place positions with conditional routing)
Tasks with variable part geometry (requires additional demonstrations or configuration)
Sequences with multiple gripper types or tool changes

Not yet within reach for non-specialists:

Sub-millimetre insertion tasks (precision electronics, tight press-fits)
Complex welding or surface-following paths
Tasks requiring custom calibration of force-torque sensors

How to Evaluate a No-Code UR Platform

Before committing, ask these questions specifically for UR compatibility:

Which UR firmware versions do you support? UR controllers go back to CB2/CB3 as well as the e-Series. Confirm compatibility with your controller version.
How does the platform connect to the UR controller? Most use the RTDE (Real-Time Data Exchange) interface or URScript push over TCP. Confirm the connection method and any network requirements.
Can it read and write UR digital I/O? For machine tending, this is essential. Ask for a demo specifically showing signal I/O in a multi-step task.
What does the output URScript look like? Request to see the generated script for a sample task. A platform that cannot show you the output code is one where you have limited ability to inspect or modify the result.
Can I load the program directly into PolyScope if I need to edit it later? Interoperability matters for long-term ownership.

UR-Specific Setup Tips for Non-Specialists

If you are doing a first installation of UR with any no-code platform:

Verify the installation angle. UR cobots behave differently when mounted overhead, floor-mounted, or wall-mounted. Confirm the robot's installation angle is correctly set in the UR controller settings — incorrect setting causes wrong trajectory calculations.
Set tool center point (TCP) accurately. The TCP is the reference point for all position calculations. If your gripper is not accurately defined as the TCP, positions will be off. Most platforms guide you through this, but confirm it explicitly.
Test E-stop before any production run. Press the E-stop, confirm the robot stops immediately, confirm the status can be reset without a specialist. This is not paranoia — it is a 30-second safety check that should precede every new program deployment.
Label all I/O connections. Digital inputs and outputs on the UR controller are numbered. Before connecting anything, label each physical connection with what it does (DI[0] = gripper open, DI[1] = gripper closed, DO[0] = machine cycle start, etc.). This documentation will save you hours when troubleshooting.

The Bottom Line

Universal Robots cobots are genuinely accessible hardware — well-documented, widely supported, and designed with usability in mind. The programming layer, however, still presents a real barrier for factories without trained robotics personnel.

No-code programming platforms are closing this gap for a meaningful and growing set of tasks. The honest picture in 2026: simple to moderate pick-place and machine-tending tasks can be set up by factory workers without specialist help, in hours rather than weeks, using demonstration-based platforms.

The tasks that are genuinely within reach today are a large fraction of what small manufacturers actually need. The tasks that remain specialist-dependent are narrowing. The direction is clear, even if the journey is not complete.

See also: