Robotics & Automation worked example

Robot Arm Speed at 61% expected cell efficiency: a worked example

This worked example runs the robot arm speed numbers for a tougher week than the baseline: 61% expected cell efficiency instead of the typical 85%. Estimate required robot TCP speed in mm/sec from target parts per hour, transfer distance per cycle, and a realistic cell efficiency.

The inputs for this scenario

  • Target output rate: 400 parts / hr (held at the documented default)
  • Transfer distance per cycle (pick-to-place): 1,800 mm (held at the documented default)
  • Expected cell efficiency: 61 % (the input this scenario stresses; the baseline uses 85)

Working through the calculation

  • The calculation starts from the formula this tool documents: Required cycle rate = target output / expected cell efficiency.
  • Required TCP speed works out to 328 mm / sec at these inputs, and this is the headline figure for the scenario.
  • Required cycle rate works out to 656 cycles / hr at these inputs.
  • Transfer distance per cycle works out to 1,800 mm at these inputs.

How this compares with the baseline

  • Against the tool's baseline example, where expected cell efficiency sits at 85% and the headline result is 235 mm / sec, this scenario comes in 39.34% above the baseline at 328 mm / sec.
  • Use it when checking whether a robot's rated TCP speed supports a demand rate, or when a long transfer distance makes a target output look questionable. A result at this level usually justifies acting on the stressed input before touching anything else, because every other figure in the table is downstream of it.

Results at a glance

  • Required TCP speed: 328 mm / sec (headline result)
  • Required cycle rate: 656 cycles / hr
  • Transfer distance per cycle: 1,800 mm

Run it with your numbers

  • To rerun this with your own numbers, open the live Robot Arm Speed calculator, set expected cell efficiency to your actual value, and adjust the remaining inputs to match your operation.

Last reviewed 2026-05-12.