Skip to content
Robot loading your CNC: the three signals your machine needs
Back to Journal
#machine tending robot#CNC automation#Intrinsic OMTS#UR5e cobot cell#CNC door interlock#open source robotics#reshaped-v3

Robot loading your CNC: the three signals your machine needs

Amir Khan

Three signals decide whether a robot can load your machine, and you can check all three standing at it in a quarter of an hour. Can the door be opened and closed by a digital output? Can the vise clamp and release on another one? Will the control take a cycle-start pulse from outside? If any answer is no, the cell you are about to cost needs an aftermarket door actuator, a pneumatic vise, or an M-code wired out to a relay board — and none of that comes with the robot or the software.

That test is now easy to apply, because the sequence a robot runs to tend a CNC has been written down in public. Intrinsic, Alphabet's robotics company, released its Open Machine Tending Solution on 22 September under Apache-2.0: a complete, stage-by-stage description of a robot loading a machine, with the source file named for each stage. You can argue with it before you buy anything.

Animated view of the OMTS machine tending cycle running in the RViz visualiser
This is RViz — a simulator, not a shop floor. From the intrinsic-omts README by Intrinsic

Where the three signals appear in the cycle

In the first stage and the fourth, which is why they gate everything. The cycle runs like this. Open the door and the vise. Move to a view frame, photograph the part in RGB-D, and work out its position in six degrees of freedom. Open the gripper, touch down under force control, retract 3 cm, grasp. Approach the machine, seat the part into the vise under compliant motion, clamp, let go, and retract in a straight line out of the enclosure. Then the handshake: arm to a safe standby position, close the door, pulse cycle start, wait for completion. Then unload and return the finished part to the infeed table. The whole thing sits in a behaviour-tree loop that runs once, a set number of times, or continuously.

Every door, vise and cycle-start action in that list goes through one skill, dio_set_output, which the README says "toggles digital outputs on the I/O controller to automate external hardware signals, such as commanding the CNC machine door to open/close and actuating the vise clamp." That sentence is the feasibility question. The design assumes your machine will do those three things on a signal, and it is silent about what to do when it will not.

Cobot-and-CNC integration itself is a decade-old trade, and automatic doors have been sold for it for years. The cost is known; what is new is that you can price the work against a written cycle rather than a vendor's demo.

Do you need a camera, or just a better tray?

A tray, in most cases, and the decision is worth making before you quote. The template offers two ways for the robot to find the part. Vision-guided pick uses a 3D camera and pose estimation for parts lying where they fall. Blind grid pick uses row-and-column arithmetic on a pallet. Fixture your parts into a tray and the camera is optional; tip them into a bin and it is not.

That is a fixturing bill against a vision bill, and the fixturing bill is usually smaller and always more predictable. It also removes a licensing question: the FoundationPose weights that make vision-guided pick work are neither in the repository nor covered by its licence. They download from NVIDIA under the NVIDIA Open Model License, and the README says plainly that Intrinsic does not distribute them. If a customer's contract has an open-source clause in it, that paragraph is worth reading twice.

Block diagram of the OMTS architecture: behaviour tree, skills and services, hardware adapters
High-level OMTS architecture, from the intrinsic-omts README by Intrinsic

What the template will not tell you

Anything about throughput. There is no cycle time, no payload, no repeatability figure and no shop on record as having run it. The production cell in the configuration folder is a UR5e with a CNC enclosure and a Schunk vise; the lab cell is a UR3e with no CNC at all; the KUKA KR10 folder is labelled a placeholder. Cobot payloads and small parts, in other words — not a pallet of castings.

It also leaves out the computer, while specifying one: x86-64 only, 32 GiB of RAM minimum and 64 recommended, a 1 TB NVMe drive, two or three gigabit Ethernet ports, and an RTX 3060 or 4060 class card "strongly recommended". That is a workstation standing next to the machine, and its price is yours to add.

So take the fifteen minutes first. Go to the machine, find out whether the door opens on a signal and the cycle starts on one, and you will know whether you are quoting a robot or a retrofit. When you know which, Vesprr's machining team can price the fixturing and the parts around it.

Sources