Catch the drift before it stops your UR arm.
UR robot arms rarely fail outright. They get nudged, slowed and worn until something gives and the robot stops. RideScan scores every run against how the robot ran on day one, so you can fix drift on your schedule, not when the line stops.
It's free for one robot for a week, and nothing on the robot changes.
See how RideScan catches drift.
Pick a change in the robot's behaviour and watch how RideScan flags each anomaly.
Risk Score Graph
Every run, scored against the calibrated baseline.
The robot runs exactly as it did at handover, so RideScan stays quiet.
How RideScan assures throughput
1Handover
| Cycle time, 38.2 s | Pass |
| 50 cycles without a fault | Pass |
| Safety functions checked | Pass |
Day 1The cell passes its acceptance test, but nothing records how it runs after that.
Day 1RideScan records how the robot runs on handover day, using 15 normal cycles.
2A small drift
Day 6A fixture shifts a few millimetres, but the robot still finishes every cycle, so no alarm goes off.
Day 6RideScan flags the change that afternoon and shows exactly when it started.
3More anomalies
- WedPaused at the pick. Reset it.
- ThuDropped a part. Cleared.
- FriSlow first cycle again?
- MonDropped another one. Reset.
Days 7 to 12The robot pauses and drops the odd part, and each time someone resets it and carries on.
Showing 5 high-risk runs, most recent first
| Risk | Time | Type |
|---|---|---|
| 31.6 | Wed 18:47 | process_file |
| 27.9 | Wed 13:30 | process_file |
| 24.2 | Wed 09:12 | process_file |
| 21.5 | Tue 16:41 | process_file |
| 18.4 | Tue 14:02 | process_file |
Days 6 and 7Every unusual run goes on the alert list with its time, so the pattern is easy to see.
4The failure point
The program has been paused. Check the cell before you restart.
Day 13Then the robot stops in the middle of a shift, and the line stops with it.
- Cell
- Cell 4, machine tending
- When
- Thu 07:00, before the shift
- Time
- 40 minutes
- Job
- Check the pick fixture. RideScan flagged it on Tue at 14:02.
Day 8Your team books the fix while the robot is still running.
5Maintenance
| Call-out and diagnostics, 1 day | £1,080 |
| Travel, 4 hours | Included |
| Total due | £1,080 |
Day 14An engineer spends a day finding the cause, and you pay for the call-out and the lost output.
Day 8The fix takes 40 minutes before the shift starts, and the score confirms the robot is back to normal.
6Throughput
Week 2The cell ships 610 parts instead of 1,000, and the orders still have to go out.
Week 2The planned 40-minute fix costs just 5 parts, and the orders go out on time.
How it works
It's free for one robot for a week, and you keep the report at the end.
We set it up with you.
It takes one short video call and no extra hardware.
You run 15 normal cycles.
RideScan uses them as the baseline for every run after that.
Every run gets a score.
Change one thing on purpose midweek and you'll see the score jump.
We go through your report.
You keep it whether or not you carry on.
Robot Baseline Report
Seven days of scores
Every run stayed at 0.01% apart from the two runs after your deliberate change.
Your alert level
It's set at 15, and any run above it goes on the alert list with the time it happened.
What we saw
What it means
RideScan caught your change on your own robot, scored it the same on both runs and confirmed when the robot was back to normal.
The report you keep
- Your robot's baseline stays on record, even when the people who set it up move on.
- Every run that week has its own score.
- Your deliberate change shows up with the time you made it and how far the score moved.
- You see it work on your own robot before you decide anything.
It works with what you already have.
RideScan runs alongside your controller and UR Connect, and it checks every run against the baseline without changing anything else.
Alongside what you run today
- RideScan checks every run against the baseline.
- UR Connect backs up programs and counts stops.
- PolyScope X runs the program and keeps the cell safe.
Works today on PolyScope X
It runs on any six-joint Universal Robots arm with PolyScope X.
If your robot runs PolyScope 5 or 3, tell us on the form and we'll show you how to connect it.
Easy for IT to approve.
RideScan needs one outbound connection and nothing inbound, and it never controls the robot.
RideScan needs one outbound HTTPS connection on port 443 from the robot controller to RideScan's cloud. Nothing connects inbound. It reads the robot's own data and sends no commands to the robot. UR Connect uses the same kind of outbound connection.
What it never touches
Your programIt adds no program nodes and no URScript.
The robot's motionIt sends no motion commands, so it can never move or stop the robot.
Your safety systemYour safety settings stay exactly as they are.
Questions
- Will it change my program or my safety settings?
- No. RideScan only reads the data the robot already produces, so your program and your safety settings stay exactly as they are.
- Which robots does it work on?
- It works on any six-joint Universal Robots arm running PolyScope X. If yours runs PolyScope 5 or 3, tell us on the form and we'll show you how to connect it.
- Will it raise false alarms?
- Not in our testing. In our UR15 field test, which used position data only, all 14 normal and extra-payload runs stayed at 0.01%, and you set the alert level yourself.
- Can it detect a change in payload?
- Yes, with effort data. Position data alone shows the arm still follows its path, so an extra load doesn't trigger an alert. When RideScan also scores how hard the joints are working, it flags the extra load as a change in behaviour. We've proven this in internal testing.
- When does it flag a problem?
- It flags the first run that looks different from the baseline, while the robot is still working.
- How long does set-up take?
- One short video call. You install the URCap from a USB stick, run 15 normal cycles, and calibration took under 15 minutes in our UR15 field test. Nothing on the robot needs rewiring.
- What happens after the free week?
- We go through the report with you, and if you want to keep scoring every run, we'll talk about it then. The report is yours to keep either way.
- I'm an integrator. Can I use it on the cells I hand over?
- Yes. You record each cell's baseline at handover, and you and your customer both see the same record afterwards.
Get your robot's baseline this week.
It's free for one robot for a week, we set it up with you, and you keep the report.
- 1We email you to book a short set-up call.
- 2You run 15 normal cycles to set the baseline.
- 3You get a week of scores and then your report.
Thanks, we'll be in touch.
We'll email you to book your set-up call.
