Robots in Architecture Forum

Robots in Architecture, Art, and Design => General Discussion => Topic started by: Dhruva on November 18, 2026, 06:40:01 PM

Title: Controlling a pellet extruder (1–10 V analog input) from a KUKA KR 120 with KRC5
Post by: Dhruva on November 18, 2026, 06:40:01 PM
Hello everyone,

I'm new to industrial robotics. I'm setting up a robotic pellet-extrusion cell for R&D and would appreciate guidance on the control side.

Setup

Robot: KUKA KR 120 with KRC5 controller
Extruder: Chinese pellet extruder with servo drive, speed set by a 1–10 V analog input.
Software: I plan to use KUKA|prc / Grasshopper for toolpaths

What I want to do
Make extrusion speed follow the robot's TCP speed, with start/stop at the beginning and end of each path.

My questions

The KRC5 has no analog outputs as standard. Which I/O module do you recommend (EtherCAT, PROFINET or EtherNet/IP), and how do you map it in WorkVisual?
How do you drive the analog voltage from KRL or KUKA|prc so that it is synchronized with robot motion?
How do you wire the extruder's enable, ready and fault signals, and connect its emergency stop to the robot safety circuit?
Are there common mistakes with grounding or noise on 0–10 V lines near a robot cabinet?
Has anyone done this with a low-cost extruder, and did you need an integrator for the safety part?

Thanks in advance. I can share the extruder's datasheet and wiring diagram if that helps.
Title: Re: Controlling a pellet extruder (1–10 V analog input) from a KUKA KR 120 with KRC5
Post by: Johannes @ Robots in Architecture on November 20, 2026, 09:15:09 AM
Hi,

I'm happy to give you some pointers here. For IOs, the simplest way that also does not cost you extra (beyond the hardware) is EtherCAT, so get an EK1100 coupler plus an analog output module (EL4xxx, I think). There are plenty tutorials on how to map the EtherCAT hardware with the robot variables, like $ANOUT[1] in WorkVisual.
The robot has got a concept that is called a submit interpreter. The file sps.sub runs cyclically in the background and you can also define your own .sub files.

So what you could do, is to create a global variable (e.g. EXTRUDE as Boolean) and then from your program (use the Custom KRL/Custom Code component) set EXTRUDE = TRUE or FALSE. In the submit program, running in the background, you then check the variable and set the extruder speed based on the actual speed of the TCP. $VEL_ACT something - please check it in the manual as I'm travelling at the moment.

That way, the extruder and TCP speed are synced. Instead of a Boolean variable, you could also create a numeric value that allows you more flow control. Or both.

Safety is something quite different and depends on the local laws and regulations. At least in the EU you would not need a fully approved safety setup for an application that is purely R&D, as yours. On the practical side, I would definitely add a line the submit file that stops the extruder if the E-Stop is on. That won't count as "legal" safety, even if it will make your setup safer to experiment with.

All the best,
Johannes