Industrial robot integration.
Fanuc, ABB, KUKA and Universal Robots.
DAXP Automation programs Fanuc, ABB, KUKA and Universal Robots and integrates them with the cell PLC, whether Siemens or Rockwell: paths, signal exchange, cell safety and HMI. We simulate offline before setting foot on site.
What we program for each brand
A well-programmed robot is one the operator knows how to recover after a fault.
Efficient paths, yes, but also recovery routines, clear messages and a PLC signal exchange that never leaves ambiguous states.
Let's talk about your cellCapabilities
Fanuc
TP and Karel programming, iRVision and ROBOGUIDE simulation on R-30iB controllers.
ABB
RAPID and RobotStudio for handling, welding and assembly, communicating with the PLC over PROFINET or EtherNet/IP.
KUKA
KRL and WorkVisual. PLC-based control with mxAutomation when the cell calls for it.
Universal Robots
Cobot programming and integration with the line PLC for packaging, food and tasks alongside operators.
Robot–PLC handshake
Well-defined start, cycle, fault and gripper signals; program and recipe selection from the PLC or HMI.
Cell safety
Fencing, light curtains and scanners integrated with the robot’s safety functions (DCS, SafeMove, SafeOperation), to the project’s safety specification.
Machine vision
Camera-guided robots with 2D vision, using iRVision on Fanuc or external vision systems, to pick parts without a fixed position or to inspect them.
Grippers and tooling
Pneumatic and electric grippers, vacuum cups and tool changers, with their confirmations included in the signal table.
Each brand has its own language and tools, but integration problems are always the same: who is in control, how the robot returns to a safe position and how the operator is informed. We answer those three questions with the same approach across all brands, so the plant has one common way of working.
How we integrate a cell
Interface first, code second.
Most robot-cell problems are born at the boundary between robot and PLC. That is where we start.
Let's talk about your cellSteps
- 01Signal table
We define the robot–PLC exchange before programming: who is in charge, what gets confirmed and what happens on a fault.
- 02Simulation
Reach, collisions and cycle time in ROBOGUIDE, RobotStudio or KUKA.Sim, even before the robot model is chosen.
- 03Programming
Robot program and PLC logic developed in parallel from the same signal table.
- 04Commissioning
Point teaching, fault-recovery testing and validation with real production.
- 05Handover
Robot and PLC backups, signal list and documentation for maintenance.
Offline simulation does not replace commissioning, but it changes what happens during it: instead of programming from scratch on site, points are fine-tuned on a program that has already run the full cycle on the computer.
Typical cells
Illustrative examples of the kind of project we work on. They are not customer references.
End-of-line palletising
Robot with several pallet patterns selectable from the HMI and a Siemens or Rockwell PLC as master.
MIG/MAG welding
Robot cell with a turntable, safety screen management and part-level traceability.
Vision-guided pick & place
2D camera guiding the robot to pick randomly placed parts, with automatic reject of defective ones.
Frequently asked questions
Do you program robots from different brands in the same plant?
Yes. Fanuc, ABB, KUKA and Universal Robots, integrated with Siemens or Rockwell PLCs. Plants often have robots from several brands depending on when each line was built.
What is the robot–PLC handshake?
It is the signal exchange that coordinates both: the PLC requests a program or cycle, the robot acknowledges it, reports its state and signals when it has finished or faulted. If it is poorly defined, the cell ends up in states nobody knows how to clear.
Industrial robot or collaborative robot?
An industrial robot is faster and carries more, but works behind fencing or guarding. A cobot is designed to share space with people by limiting force and speed, although each application still needs to be assessed. It depends on the task, payload and pace.
Can you reprogram a robot that is already installed?
Yes. We take a full controller backup before touching anything and document the changes.
Can you simulate before buying the robot?
Yes, and it is a good idea: simulation checks reach and cycle time before the model is chosen.
What do you need to simulate the cell?
The 3D model of the cell or at least of the parts, fixtures and guarding; the intended robot model and the operating sequence. With that, reach, collisions and an indicative cycle time can be checked.
Does robot safety (DCS, SafeMove) replace guarding?
It can reduce the guarded area or allow shared zones by safely limiting robot positions and speeds. Whether that is enough is determined by the machine risk assessment, which is the responsibility of the machine owner.
What does a robot cycle time depend on?
On the path, the payload, the gripper and the waits with the rest of the cell. Simulation gives an estimate before buying, and the bottleneck is often not the robot itself but the signal waits with the PLC.
Planning a robot cell?
Tell us which task you want to automate, with which robot and on what timeline.