3D vision and scan processing.
Noisy scans turned into clean geometry the robot can use: edges, surfaces, and where the part actually sits in the gripper.
Robotics — Software for Robot Cells
Software for industrial robot cells.
When every part is different, one taught program won't fit. We build the software that turns 3D scans into robot programs, checks each part before the robot moves, and plugs into your cell.
Book a 30-minute callWhat we build.
A program for each part.
Paths, tool angles, and moves onto, off and around the part, worked out from the scan while the cell waits.
Checks before the robot moves.
The scan is compared with the part you expect. A normal shift is corrected automatically; anything else triggers a rescan or a stop.
Integration with your cell.
Output written in the controller's own conventions, with simple rescan and stop signals for the cell software's retry loop.
How we build it
Robot software has to be kept running by the people who run the cell. We build it like production software: automated tests on every release, an independent check before each delivery, and output that is the same every time it runs. Where the job allows, it runs on the cell PC with standard libraries, with no simulator licence and no GPU.
Example: scan-to-path sanding on a KUKA cell
A KUKA KR 50 robot picks up a chair shell, scans it with a 3D camera, then sands the edges with a force-controlled disc and the faces with a brush. Every shell is a little different and sits up to ±20 mm differently in the gripper, so a program taught once doesn't fit.
What we built
- One seamless curve through each scanned edge. The usual method left a 1.4–13 mm gap with kinks up to 105°; ours closes with no gap.
- Tool positions that keep the disc square to the edge, with half the points within 0.55 mm of the measured edge.
- The full sanding program, including brush strips that cover 100% of the surface at even pressure, where a single strip missed 8–10%.
- Checks that catch a part loaded the wrong way round, before the robot moves.
~2.5 s
from scan to first edge program
~20 s
for the full set, on an ordinary laptop
1,935
automated tests
7 releases
in 5 weeks
Tekhouse also builds software for banks and fintechs, and helps companies change how they deliver it. See all services
Questions
Which robots do you work with?
Our delivered example runs on a KUKA KR C5 controller. The scan, path and check logic doesn't depend on the robot brand, and the output is written in your controller's conventions. Tell us what you run on the call.
What does the first step look like?
A 30-minute call about your cell, your parts and what isn't working. If there's a fit, we agree the scope and price before any work starts.
Thirty minutes about your cell.
Tell us about the parts, the cell and what isn't working. No pitch, no obligation.