Online support for changes to ABB robot programs

You make the change. With us and Robin alongside

A new product variant, gripper or cell. We support your team online: we consult on the change, work on it together with Robin and check it before it reaches the line.

  • 10 h blocks · €1,400 net
  • Fully online
  • IRC5 and OmniCore
R3 · NEW GRIPPERreviewing…
- PERS tooldata tGripper:=[TRUE,[[0,0,150],…+ PERS tooldata tGripper2:=[TRUE,[[0,0,185],…  PROC PlaceBox()    MoveL pPlace, v1000, z10, tGripper2;    SetDO doGrip, 0;    MoveL pRetract, v1000, z50, tGripper2;  ENDPROC
  • ✓New gripper datatooldata: matches the gripper datasheet
  • !pPlace with zone z10, then SetDO right afterthe gripper would open before reaching the point: use fine here
  • ✓Retract after placing, no collisionoffline test in RobotStudio
Illustrative exampleYour team makes the decision

How it works

Support in blocks of hours

You buy a block of hours and use it when you need it.
The code stays yours, and you decide on the upload.

  1. 1

    Call: what you are changing

    We agree what the change is about, on which robot and when it needs to be on the line.
    We suggest how many support hours you may need.

    What you keepProposed block of hours
  2. 2

    Choosing a block of support hours

    €1,400 net per 10-hour block. You see every hour used in the log.

    What you keepA log of the hours used
  3. 3

    Joint online sessions on a copy of your program

    We work together remotely on a copy of the program, so the line keeps running on the current one. We consult on the tricky parts and help prepare the change.

    What you keepThe change prepared on a copy of the program
  4. 4

    Review and offline test before upload

    Before upload we review the whole change and check it in RobotStudio on a copy of your program.

    What you keepThe change checked offline and documented
  5. 5

    Upload when you decide

    Your maintenance team decides whether and when to upload the change.

    What you keepA documented program after the change

Change review

What we look at before a change reaches the line

Six things we check in a review.

Tool and load

Whether the gripper and part data match reality.

Points and zones

Where the robot must reach the point exactly, and where it can “cut the corner”.

Signals and sequence

Whether the robot and PLC wait for each other in the right places.

Error handling

What the robot does when something goes wrong.

Collisions

If you have a cell model in RobotStudio, we check new moves in it before the robot runs the program on the line.

Change description

Whether someone else will understand in six months what changed and why.

Example from a review

A new part type with no handling for unknown numbers

The team added handling for a new part type.
When the PLC sends a number the program doesn't know, the robot silently skips the whole block: it does nothing and nobody knows why.

In the review we add DEFAULT: the robot stops and shows on the pendant which number it got.

TEAM'S CHANGEMainModule
PROC rSelectPart()  VAR num nType;  nType := GInput(giPartType);  TEST nType  CASE 1:    rPickA;  CASE 3:    rPickC;  ENDTESTENDPROC
Unknown type: empty cycle with no message
AFTER REVIEWMainModule
PROC rSelectPart()  VAR num nType;  nType := GInput(giPartType);  TEST nType  CASE 1:    rPickA;  CASE 3:    rPickC;  DEFAULT:    TPWrite "Unknown type: "\Num:=nType;    Stop;  ENDTESTENDPROC
Unknown type: stop with a clear message on the pendant

Straight talk

When support makes sense, and when it doesn't

✓Makes sense when

  • Someone on your team programs, but the change goes beyond what they do day to day.
  • A new product variant, gripper or cell is coming and the program has to change.
  • You want a second pair of eyes before the change reaches the line.
  • You want to see how AI works with your program before deciding on Robin for your plant.

✕Doesn't make sense when

  • Nobody on the team programs. Then support alone won't be enough: talk to us first and we'll suggest where to start.
  • The program runs, but the line keeps stopping. Then optimization will serve you better than support.
  • Your robots aren't ABB. We work on ABB robots only.

What we don't do

Changes on your team's behalf

In this service your team makes the change and we help get it right. A new program from scratch is a separate conversation.

Migrations without you

We move programs between IRC5 and OmniCore together with your team. We don't change the safety configuration.

Uploads without your decision

A change reaches the line when your maintenance team decides it should.

Someone else decides?

To forward to your manager

Need support with a change, 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

A change on the line with no surprises

  • The change is checked offline before it reaches the line.
  • Your team sets the upload date.
  • The program is documented, so the next change is easier.
Maintenance

Your code, our support

  • The code stays yours: you understand it because you worked on it yourselves.
  • Online support when you need it.
  • You see Robin at work on your program.
Finance and purchasing

A block of hours known up front

  • €1,400 net per 10-hour block.
  • You see every hour used in the log.
  • No travel costs: support is online.
Piotr Ozga

Review 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. I know which changes work in RobotStudio but stop the robot on the line.

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 support with changes

How much does support cost?

€1,400 net for a 10-hour block. You use the hours for consultations, working with Robin and reviewing the change.
Prices for companies outside Poland. EU companies: VAT reverse charge.

Can you write the change for us?

No. Your team makes the change; we work with you online and review it before upload. If nobody on the team programs yet, talk to us first and we'll suggest where to start.

What is Robin?

Our AI assistant for ABB robots. It reads programs, event logs and backups and, once approved, improves the program. In our sessions we work with it on your program. More about Robin

What do we need to prepare?

A backup of the robot before the change and a description of what should change.

Do you need to be on site?

No. Support is online: joint sessions and work on a copy of the program.

Who is responsible for uploading the change?

Your maintenance team decides on the upload and its timing.

Which controllers do you work with?

IRC5 and OmniCore, ABB robots only.

First step

Describe your change

Tell us in a few words what you're changing and by when.
We'll reply with how many support hours you may need.

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