Diagnosis | Optimization | Support

Efficient robotics for manufacturing plants

We make ABB industrial robots work better: we diagnose and improve your programs and support your team when the line changes.

R1 · PALLETIZINGPCS 0127OEE 94%

Services

How we can help

The program runs, the line stops

ABB robot program optimization

We start with a diagnosis from the backup and event log. Fixes from the report are prepared offline and go live only with your maintenance team's approval.

  • Error handling: the robot recovers on its own
  • Zones and return to home position
  • Loads, paths, cycle time
  • Faster restart after changeover
What the diagnosis looks like
The program has to change · online

Support with changes to ABB robot programs

A new product variant, gripper or cell. We support your team online, together with Robin, in a block of hours.

  • Online consultations during the change
  • Working with Robin on your program
  • Review and offline test before upload
  • A written description of the change that stays with you
What support looks like
Our product · waitlist

Robin: AI assistant for ABB robots

Reads programs, event logs and backups, and improves the program once you approve the change.

  • Reads the event log and the backup
  • Proposes a change you can review
  • Nothing goes to the robot without your approval
  • Built by an ex ABB robot trainer and integrator
Join the waitlist

How we work

Every project starts with a conversation

Working with us, you know up front what happens after our first call.

StartConversation

Free consultation.
Tell us what you're dealing with and what you expect.

What do you need?

  1. 1Diagnosis from backup and event log
  2. 2Report: list of improvements with pricing
  3. 3Changes prepared offline
  4. 4Rollout and test on the line
  5. 5Summary report of the changes
  1. 1Call: what you are changing
  2. 2Choosing a block of support hours
  3. 3Joint online sessions on a copy of your program
  4. 4Review and offline test before upload
  5. 5Upload when you decide

Examples from audits

What we usually find in ABB robot programs

Most stops aren't caused by a robot failure, but by a program that wasn't thought through.
Two typical cases.

01

The robot stops “for no reason” a few times a week

The gripper mass in the program doesn't match reality. The robot reads this as a collision and stops.

FixSetting the correct load data.

R2 · PACKING LINE · IRC5analysing…
50204 Motion supervision · 3rd stop this week
  1. Analysing the R2 backupEvent log analysis · 14 stops on the same move
  2. Causegripper tooldata: 2 kg in the program, about 6 kg in reality
  3. Fixnew load data from identification (LoadIdentify)
- PERS tooldata tGripper:=[TRUE,[[0,0,150],[1,0,0,0]],[2,[0,0,50],…+ PERS tooldata tGripper:=[TRUE,[[0,0,150],[1,0,0,0]],[6.1,[0,0,92],…
Waiting for maintenance approvalRejectApprove
Illustrative example: a typical finding from a program audit.
02

The robot stops with errors

The robot searches for a part on the stack with a sensor. When the stack is empty, it stops and waits until someone from maintenance walks over to the pendant. With error handling, it backs off to Home and reports the problem to the PLC.

BEFOREMainModule
PROC rPickFromStack()
  MoveJ pAboveStack, v1000, z50, tGripper\WObj:=wobjFixture;
  SearchL \Stop, diSensor, pTop, pBottom,
          v100, tGripper\WObj:=wobjFixture;
  MoveL pTop, v50, fine, tGripper\WObj:=wobjFixture;
  SetDO doGripClose, 1;
  WaitDI diGripClosed, 1;
  MoveL pAboveStack, v500, z50, tGripper\WObj:=wobjFixture;
ENDPROC
ERR_WHLSEARCH · empty stack, robot stopped with an error
AFTERMainModule

Empty stack: back to Home, message to the PLC, program ends

Client feedback

What clients say

Piotr has enormous knowledge of robotics. After the training sessions I attended, I knew there was no problem he couldn't solve. Most importantly, he has very strong soft skills, which makes his training very effective.
Mariusz MaślakMaintenance Manager
Deep knowledge of robotics. Piotr could answer every programming question we had. You could see the passion, commitment and professionalism.
Mikołaj CiokAutomation and Robotics Section Coordinator
The training was top level, both in content and in how we were looked after. Learning systems that were new to us was a real pleasure.
Jarosław TesmerPLC & Robot Software Engineer

Quotes translated from Polish.

Piotr Ozga

Who's behind it

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. Today I pass that experience on to your team.

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
Our product

Robin: AI assistant for ABB robots

It reads programs, event logs and backups and, once you approve, improves the program.

See Robin

Before you ask

What we hear most often

Optimization“Will it pay off at all?”

Before we start, we agree with you how we'll measure the effect: how often the robot stopped the line, how long it took to clear a fault, how often you called service, how long the restart after a changeover took. Before anything is implemented, you get a report: where you are today and what we expect after the changes. You decide on next steps based on it.

All services“How much does it cost?”

Optimization: the diagnosis alone is €650 net per robot, followed by a specific quote.
Online support: €1,400 net for a 10-hour block.
Prices for companies outside Poland. EU companies: VAT reverse charge.

First step

The first step to more efficient production

Tell us in a few words what you need: a diagnosis, a program fix or support with a change.
We'll reply with a proposed first step.

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