ABB robot program optimization

The program runs, but the line keeps stopping

We start with a diagnosis based on the backup and event log. Then you get a report: what to fix, in what order and what it costs. You can stop at the report.

  • Diagnosis: €650 net per robot
  • Report in 5 business days
  • IRC5 and OmniCore
DIAGNOSIS REPORT · LINE 3ROBOTS R1–R6
Error handling in pick routinesrobot stops instead of retrying the grip3 missing
R2 gripper load dataalarm 50204 on the same movemismatch
Return to home after a stopmaintenance walks over after every stopmanual
Operator permissionsoperators can change more than they shouldtoo broad
R4 zones and speedscycle timeto check
Other robotsno recurring alarmsOK
ORDERR2 and error handling first: the most stops fixed with the smallest change.
Illustrative exampleYour report is built from your backup

How it works

From backup to a smoother line

We diagnose programs from the backup, prepare fixes offline and roll them out together with your maintenance team.

  1. 1

    Diagnosis from backup and event log

    You send the robot backups and the event log. We read the programs, configuration and alarm history. Together we also agree what we'll measure at the end: line stops, time to clear faults, service call-outs, changeovers.

    Your timeTaking and sending the backup
  2. 2

    Report: list of improvements with pricing

    What stops the line, on which robot and why. Fixes ranked by payback and pricing for the scope you choose.

    What you keepReport with fixes and pricing
  3. 3

    Changes prepared offline

    We prepare the fixes you choose from the report and test them in RobotStudio on a copy of your program.

    What you keepDocumented changes for maintenance approval
  4. 4

    Rollout and test on the line

    We upload approved changes together with your maintenance team and check them in production. You choose how: remotely, included in the scope, or on site at extra cost.

    What you keepA working program and a copy from before the changes
  5. 5

    Summary report of the changes

    We compare what we agreed at the start: line stops, time to clear faults, service call-outs.

    What you keepBefore-and-after comparison

Diagnosis from backup

What we check in your ABB robot programs

We do it with Robin, our AI assistant for ABB robots.
A person checks and writes up every finding.

Causes of stops

Which alarms repeat, on which move and why.

Error handling

Where the robot stops even though it could safely recover on its own.

Cycle time

Zones, speeds and load data that stretch the cycle.

Restart after changeover

What slows the line's return to work after maintenance or a format change.

Permissions and operation

What operators can change but shouldn't.

Plan with pricing

Fixes ranked by payback, with a price for the scope.

Example from a diagnosis

The robot stops in mid-air

Via points are programmed as fine, which makes them stop points.
The robot stops at each of them, even though it does nothing there.

Switched to zones, it rounds them off without stopping.
The point where it places the part stays fine.

BEFOREMainModule
PROC rMoveToPress()  MoveJ pVia1, v1000, fine, tGrip;  MoveJ pVia2, v1000, fine, tGrip;  MoveL pAppr, v500, fine, tGrip\WObj:=wobjPress;  MoveL pPlace, v100, fine, tGrip\WObj:=wobjPress;ENDPROC
The robot stops at 3 via points every cycle
AFTERMainModule
PROC rMoveToPress()  MoveJ pVia1, v1000, z50, tGrip;  MoveJ pVia2, v1000, z50, tGrip;  MoveL pAppr, v500, z10, tGrip\WObj:=wobjPress;  MoveL pPlace, v100, fine, tGrip\WObj:=wobjPress;ENDPROC
No stops on the way · we measure the cycle gain before and after

Straight talk

When program optimization makes sense, and when it doesn't

Optimization helps when the cause is in the program.
If the problem is somewhere else, we'll tell you on the first call.

✓Makes sense when

  • The robot stops a few times a week on the same alarms.
  • Maintenance has to walk over after every stop, because the robot doesn't recover on its own.
  • After a changeover or maintenance, the line takes a long time to get back to normal.
  • The program has passed through several hands and nobody at the plant knows all of it.

✕Doesn't make sense when

  • The problem is mechanical: gearbox, cable, motor. That's a job for the manufacturer's service.
  • You need a new program or a new cell from scratch.
  • Your robots aren't ABB. We work on ABB robots only.
  • The line stops because of the PLC or equipment next to the robot. The diagnosis will show it, but we fix the robot program.

What we don't do

Changes without your approval

No fix reaches the line before your maintenance team signs it off.

Lock-in

Every change is documented in the program and in the report. Your team knows what we changed and why.

Packages “just in case”

We only price the fixes you pick from the report. You can do the rest yourselves.

Someone else decides?

To forward to your manager

Want to order a diagnosis, but someone else makes the call?
Here are the answers to the questions your production director, maintenance manager and finance team will ask.

Production director

Fewer stops, visible in the numbers

  • At the start we agree what we measure: line stops, time to clear faults, service call-outs.
  • After the rollout you get a before-and-after comparison.
  • The diagnosis doesn't stop production: we work on a copy of the program.
Maintenance

Control over every change

  • Your team only spends time on a call and sending the backup.
  • You approve every change before upload; the copy from before stays.
  • Changes are documented, so you still understand the program yourselves.
Finance and purchasing

Cost known before every step

  • The diagnosis has a fixed price: €650 net per robot.
  • Remote rollout is included in the scope price; on site: €1,200 net per day, plus travel at cost.
  • The scope of fixes you pick is priced before you order anything.
  • You can stop at the diagnosis: the report is yours to keep.
Our product

Robin: AI assistant for ABB robots

It helps us with the diagnosis.
It reads programs, event logs and backups and, once you approve, improves the program.

See Robin
Piotr Ozga

Diagnosis by

Piotr Ozga

I've worked in industrial robotics for 10 years. I've seen ABB robots from every side: as a trainer, as a programmer in a factory and at the line during commissioning. The cause of a stop is rarely the robot itself. More often it's the program.

1000+people trained on ABB robots
6 yearsas an ABB robot trainer
7700+engineers follow on LinkedIn
Co-authorof the “RobotStudio goes to university” programme
SpeakerInfoshare 2026 · 18 November, Katowice

Before you ask

Questions about diagnosis and optimization

How much is the diagnosis?

Fixed price: €650 net per robot, whatever we find. Fixes are priced separately, for the scope you choose from the report.
Prices for companies outside Poland. EU companies: VAT reverse charge.

How long does the diagnosis take?

You get the report within 5 business days of us receiving the backup.

Do we need someone from our team?

Only for a 30-minute call and to send the backup and event log.
We do the rest.

What happens to our backup?

It's used only for the diagnosis. We analyse it with Robin, and parts of the program go to an AI model with training on your data switched off. We delete the backup after the diagnosis or, if you go ahead with the fixes, once they're rolled out. We sign an NDA on request.

What if the diagnosis finds nothing?

That's a result too: you know the cause of the stops is outside the robot program, and you get a pointer on where to look next.

Do we have to order the fixes after the diagnosis?

No. The report is yours. You can implement it yourselves, order selected fixes, or book online support while your team makes them.

Do you upload changes without us?

No. Your maintenance team approves every change before it's uploaded, and we upload it together with you. A copy of the program from before the changes stays with you.

Do you come on site?

If you want us to. We can do the rollout remotely, on a video call with your maintenance team, included in the scope price. On site: €1,200 net per day, plus travel at cost.

Which controllers do you work with?

IRC5 and OmniCore, ABB robots only.

How will you check the fixes worked?

At the start we agree what we measure: line stops, time to clear faults, service call-outs, changeovers. After the rollout we compare the same numbers.

First step

Tell us where your line stops

Tell us in a few words which robot stops and how often.
We'll reply whether a diagnosis makes sense for you.

No obligationWe reply within 1 business day

Data controller: Piotr Ozga Smart Robot Skills. We use your data only to reply to your enquiry. Privacy Policy