Home About Expertise Projects Blogs Contact
RoboticsKRL ProgrammingOptimisationCompleted

KUKA KR10
Cycle Time Optimisation

A pick-and-place program on a real KUKA KR10, rewritten so the path does the work. Same speed, about 2 seconds faster per run.

TypeLab practical · robot programming
DomainIndustrial automation
RobotKUKA KR10 · KR C4 · KRL
ToolssmartPAD · Autodesk Fusion 360
CourseUCD MEEN41350 Introduction to Robotics
By Chandan NaveenPublished 18 November 2026Updated 18 November 2026Reading time: 7 min
-3%
Cycle time at the same speed
67.17 → 65.13 s
Video timing, baseline to optimised
4
Bottles picked and placed per run
0
Speed or acceleration changes
01 · The brief

Energy was the plan, time became the metric

Project 2 of our robotics module at UCD was a practical study in a group of five. The task was to program a pick-and-place routine on a KUKA robot, set a baseline, change one thing at a time and see what it did to energy use. I designed the path, programmed it on the pendant and ran the optimisation.

Energy needed a data acquisition box and clip-on sensors, and that setup was not ready on the day. We were told to compare runs without it. So the question became simpler: how much shorter can a cycle get if the robot does not move any faster? A shorter cycle does not prove lower energy, but a robot draws power the whole time it runs, so the two usually move together. I did not measure that and I will not claim it.

This sits next to my work on robots in the electronics industry and the KUKA.Sim cell. There the robot was virtual. Here it was a real arm with a real pendant.

02 · The setup

A real arm, four bottles

The robot was a KUKA KR10, a six-axis industrial arm on a KR C4 controller. I wrote the program in KRL on the smartPAD teach pendant and ran it in T2 mode, where the robot moves at programmed speed only while the Start key is held.

The task was short. Start from home, open the gripper, pick four bottles one after another, place each at a drop position, return home. I also designed the bottle holder in Autodesk Fusion 360 and supplied the CAD for it, so the bottles sat in the same place on every run.

ItemDetail
RobotKUKA KR10, 6 axes
ControllerKR C4, KUKA System Software
LanguageKRL, written on the smartPAD
ModeT2, test mode at programmed speed
TaskPick 4 bottles, place each at a drop point, return home
ProgramsOne baseline, one optimised
LabLIMAR lab, UCD
03 · The baseline

Get it working, then look at it

The first program only had to work. I ran it at 75% and at 100% of the pendant's speed override, which is the speed setting on the pendant. Then I watched it and wrote down what looked wasteful.

04 · What I changed

Better path, same speed

Speed and acceleration stayed exactly where the 100% baseline had them. Any gain had to come from the path.

01

Closer approach and retract points

I moved them as near to the bottles as was safe, so the arm lifts and lowers less on every pick and every place.
Approach · Retract
02

Smoother via points

I did not switch on KUKA's blending setting. I repositioned the points by hand so the arm moves in a continuous path and does not nearly stop at each point.
Via points
03

No wasted axis rotation

One axis was swinging back and forth between points. Choosing better points removed that motion.
Joint motion
04

Shorter pick-to-drop path

I shortened the carry and smoothed the return to the next pick.
Path length
05 · How it was measured

Two clocks, one answer

Cycle time here means the robot leaving home to the robot returning home, covering all four bottles. I timed it twice. A phone stopwatch gave a quick number, good to about 0.2 seconds. The lab video, timed frame by frame at 30 frames per second, gave a number anyone can check, good to about 0.03 seconds.

The two methods agreed within 0.4 seconds. The stopwatch read about 0.3 seconds short each time, which is the delay of pressing a button by hand. The video was not filmed for the 75% baseline, so that row has a stopwatch time only.

06 · The results

About two seconds, from the path alone

Baseline, 75% speed69.99 sBaseline, 100% speed66.88 sOptimised, 100% speed64.76 sBars start at 60 s so the difference is visible. Stopwatch times.
Cycle time for four bottles, home to home. Same speed, different path.
RunStopwatchVideo, frame by frame
Baseline, 75% speed69.99 snot filmed
Baseline, 100% speed66.88 s67.17 s
Optimised, 100% speed64.76 s65.13 s
-2.1 s
Per run, same speed (stopwatch)
-3.2% / -3.0%
Stopwatch / video
-4.4%
Baseline 75% to 100% speed

Going from 75% to 100% speed saved 3.1 seconds. The path changes saved 2.1 seconds with no speed increase at all, about two thirds of what a 25 point speed rise gave. Against the 75% baseline the optimised run at 100% was about 7.5% faster in total.

A speed rise helps less than you would expect. The gripper action and the settling at each point do not get faster when the override goes up, so part of every cycle stays fixed.

07 · What I took from it

What this changed in how I work

Path design is a lever people skip. Fewer stops, less vertical travel and no wasted joint motion cut time, and they also cut wear on the arm. If this cell ran around the clock, two seconds a cycle would turn into a lot of extra parts per shift for free. That is lean thinking applied to a robot: remove the motion that adds nothing.

Measure with two methods. A hand stopwatch is fine when something else checks it. And plan for the lab not behaving. The energy rig was not ready and the controller threw a fieldbus warning (KSS10094, a communication fault with a device on the bus). The warning did not stop the robot, but it reminded me that real equipment rarely follows the plan, and a sound backup metric kept the study useful.

What this result does not show
This is one cell, four bottles, one operator and a handful of runs. The 3% gain says nothing about energy, and I would not expect it to carry over to a different layout without testing it again.
KUKA KR10KRLsmartPADCycle timePath optimisationPick and placeAutodesk Fusion 360Lean thinking
08 · FAQ

Common questions

Can you cut a robot's cycle time without raising its speed?
Yes. In this study the optimised path finished about 2.1 seconds faster than the baseline with speed and acceleration left exactly the same. The gain came from shorter approach and retract moves, smoother paths through the via points and one wasted axis rotation removed.
Why did you measure cycle time and not energy?
The brief was about energy. The plan was to measure it with a data acquisition box and clip-on current and voltage sensors, but that setup was not ready on the lab day. The group was told to compare the runs without energy data, so cycle time became the metric. Energy was not measured, so any energy saving here is a likely effect and not a result.
How was the cycle time measured?
Two ways. A phone stopwatch by hand, accurate to roughly 0.2 s, and the lab video timed frame by frame at 30 frames per second, accurate to roughly 0.03 s. The two agreed within 0.4 s, and the stopwatch read a little shorter each time, which is the usual button delay.
What is KRL and what does T2 mode mean?
KRL is KUKA Robot Language, the programming language of KUKA controllers. T2 is a test mode where the robot runs at the programmed speed but only moves while the Start key is held, which keeps the person at the pendant in control.
Related projectKUKA.Sim SCARA PCB assembly simulation →