Skip to content
rbx.service

Robot programming

We program and optimise six-axis robots, cobots and vision systems for demanding production lines, with startup validated in simulation.

Proven on line
1,000+

Robots programmed across welding, handling, painting, assembly and vision-guided processes.

10+

OEM standards mastered (VASS, BMW, Tesla…)

On-site

Engineers on the floor through ramp-up

01 Definition

What is industrial robot programming?

Industrial robot programming is the development of the paths, logic and signals that make a robot do its job inside a cell: welding, handling, painting, assembly or vision-guided work. We do it offline on the cell simulation, in RobotStudio, Process Simulate or the OEM environment, then fine-tune it on site.

02 Simulation

Paths and cycles optimised before touching the real robot, in simulation.

We generate and debug offline programs against the cell model: we hit target cycle times and rule out collisions before the physical startup.

03 Offline robot programming

Process automation for industry

  1. Six-axis

    KUKA, ABB, Fanuc and Yaskawa in production.

  2. Cobots

    Safe collaboration between people and machines.

  3. Machine vision

    Guidance and quality control, integrated.

  4. Offline programming

    From CAD to the cell without stopping the line.

OEM standards we work to
  • [ Volkswagen, Audi, Seat, Skoda (VASS5, VASS6) ]
  • [ BMW (L7, LU, V8, TMO3) ]
  • [ Daimler (Integra Wave 6) ]
  • [ Tesla ]
  • [ Ford ]
  • [ JLR ]
  • [ Volvo ]
  • [ SICAR ]
  • [ GM ]
  • [ Stellantis ]
04 Capabilities

What we deliver

  1. Offline programming

    Native programs built in RobotStudio, ProcessSimulate or the OEM's environment, validated against the digital line.

  2. Virtual commissioning

    Every routine exercised collision-free with simulated PLC, safety and cycle timing before shipping to the plant.

  3. Controller and I/O integration

    Signal mapping, fieldbus configuration and fence-zone logic so the robot plays cleanly with the rest of the cell.

  4. Technology parameterisation

    Welding, gluing, screwing, manipulation and vision set up to the spec of the process and the product.

  5. On-site commissioning

    Deployment, tuning and go-live with the team that wrote the program. Not a handoff.

  6. Production support

    Operator training, documentation and post-launch tuning until the line runs as designed.

05 Commissioning

The RBX Programming automated process

  1. Phase 01

    Offline programming

    Paths and cycles built on the cell simulation, to your OEM standard.

  2. Phase 02

    Virtual validation

    Collisions, reach and cycle time verified before touching the real robot.

  3. Phase 03

    On-site commissioning

    Deployment and fine-tuning on the plant floor by the same team that programmed.

06 Case study

111 robots validated before Power On.

On the body-in-white line from our virtual commissioning case study, the programs for 111 robots were developed offline and tested against the digital twin, together with the logic of 9 PLCs, before a single machine was connected. All that was left on site was verification: the line reached full production in week 25.

111

Robots programmed offline and validated in the digital twin.

3

Validation cycles at startup, against 6 in a traditional launch.

25

Weeks to full production, against 53 with the traditional model.

Note

Source: case study published on our blog (body-in-white line, US electric vehicle manufacturer). The traditional baseline is for programmes of comparable scope.

07 Comparison

Offline robot programming versus teach-pendant programming.

  1. Where it is programmed

    With a teach pendant, on the real robot with the cell stopped. Offline, on the 3D model of the cell while the equipment is being installed.

  2. Collisions and reach

    With a teach pendant they are found by moving the robot. Offline they are checked in simulation before the robot is on site.

  3. Cycle time

    With a teach pendant it is measured at the end. Offline it is optimised from the start, tuning paths and waits between robots.

  4. What is left for the plant

    Offline, only fine-tuning: touching up points to the real geometry and verifying safety. Everything else arrives tested.

08 FAQ

Frequently asked questions

Which robot brands do you program?
ABB, KUKA, FANUC, Yaskawa, Stäubli and Comau, both six-axis robots and cobots. We program in each brand's native language and, where one exists, to the OEM's programming standard.
What is offline robot programming?
It means programming the robot on a virtual model of the cell instead of on the real robot. With RobotStudio, Process Simulate or the OEM environment we generate paths, check reach and collisions and validate cycle time, so the program reaches the plant nearly finished.
Which applications do you program?
Robot programming for welding, handling, painting, gluing, screwdriving, assembly and vision guidance. In each case we parameterise the process technology to the product specification.
Do you program vision-guided robots?
Yes. We integrate machine vision for robot guidance and quality inspection, configuring the signal exchange between camera, robot and PLC inside the cell.
Do you work to automotive OEM standards?
Yes. We program to the standards of Volkswagen Group (VASS5 and VASS6), BMW, Daimler, Ford, JLR, Volvo, GM and Stellantis, among others, with their program structures and interface signals.
Who handles on-site commissioning?
The same team that programmed the robots. We deploy, fine-tune and support the ramp-up on site, then train operators and support production, with no hand-offs between suppliers.

Download the case study

Request a demo