How to calculate cobot cycle time: loop seconds, line takt, and safety factor

Cobot cycle time calculation: sum pick, move, place, EOAT open-close, and waits—then compare to line takt; apply a 1.1–1.3 safety factor. Collaborative robotic arm loop-time checklist.

Roooll cobot cycle time guide: sum pick, move, place, EOAT, and waits—then compare loop seconds to line takt with safety factor

Quick answer

Formula: cycle time ≈ Σ (pick + move + place + EOAT open / close or vacuum build / vent + waits / settle)

Gate: stable cycle (with safety factor) must be ≤ line takt (seconds per piece)

Safety factor: about 1.1–1.2 for simple cells; often up to 1.3 with vision / multi-sensor coordination

Definition: catalog max TCP speed ≠ your stable cobot cycle; lock on the worst path and slowest loop

Pair with sizing: do not chase takt before payload and reach clear → Payload guide · Reach guide

The pendant stopwatch shows a “best loop” of 5.1 s against a 6 s takt—looks fine. By week two of production, vacuum retries once, vision takes an extra shot, and place waits for the tote. The slowest loop hits 6.8 s and the downstream queue grows. The fight is not “the arm is too slow.” It is treating the demo’s fastest loop as everyday cycle time. Below: cycle vs takt, a full vacuum segment table, a CNC door / chuck overhead example, safety factor, PPH, dual grip, and the cycle–EOAT–payload cross-check.

What cobot cycle time and line takt mean

Cycle time is the real seconds for a collaborative robotic arm to finish pick → place → return to a repeatable start, including arm motion and EOAT or equipment waits. MFG Calcs frames the sum as motion segments plus dwell / wait segments; the FIRGELLI cycle-time estimator multiplies the raw sum by a safety factor before talking throughput. Line takt is the average outbound interval the order or process requires—your target, not a number the arm invents.

TermMeaningHow to use it
Cycle timeFull-loop secondsCompare to takt
Line taktTarget s / pieceAcceptance floor
Motion segmentsApproach, transfer, retractBudget worst path
Process / dwellGrip, vacuum, inspect, wait equipmentOften skipped
Safety factor SF~1.1–1.3 marginAbsorbs variation and handshakes
PPH3600 / stable cycle secondsThroughput only after SF

Why the “fastest loop” lies

Demo paths are usually shortest, lightest, one-shot vacuum, and free of line handshakes. Production paths include farthest points, heaviest SKUs, leak retries, vision NG reshoots, and conveyor interlocks. The failure mode is not a lying controller—it is a commercial promise that used the demo denominator. Acceptance language should be: stable cycle (with SF) ≤ takt, locked on both average and slowest loop.

Step-by-step calculation

List every beat: pick, grip / seal, transfer, place, release / vent, retract, plus inspection / cure / equipment waits

Split arm-moving vs waiting—gripper, vacuum, vision, conveyor, and machine doors all count

Budget farthest point, heaviest part, awkward pose—not the pretty demo path

Add settling (often 0.2–0.5 s) and handshake delays

Raw sum × safety factor (1.1–1.3), then compare to takt; quote PPH = 3600 / stable cycle seconds

Run 20–30 real-part loops; lock average and slowest loop. Dual-grip math: Robotiq dual gripper

Worked example 1: vacuum pick-and-place (full segment table)

Target takt 6.0 s/piece. Single-cup vacuum rough sum:

SegmentContentSeconds
ApproachAbove pick0.5
Vacuum buildSeal + pressure OK0.8
TransferTo place zone1.2
Place / locateDescend + locate0.6
VentRelease0.4
RetractReturn to start0.7
SettleAnti-bounce0.3
Arm + EOAT subtotal4.5
Vision OK waitShot / judge1.0
Raw total5.5
× SF 1.15≈ 6.3

6.3 s > 6.0 s takt—already over. Cut waits or path, evaluate dual grip, or change EOAT path—do not pretend the 5.1 s demo ships. EOAT open-close still open → End-effector guide; path length and base → Workcell layout guide. Soft shortlist while you edit the segment sheet: Side-by-Side Comparison.

Worked example 2: CNC tending (door / chuck overhead)

Target takt 12 s/piece (in-cut time not on the arm’s critical path). Arm-side rough sum: pick blank 1.0 + approach door 0.8 + wait door open 1.5 + chuck place / clamp handshake 2.0 + spindle permit 1.0 + pick finished 1.2 + exit door 0.8 + place tote 1.0 + EOAT open-close 0.8 ≈ raw ~10.1 s. With SF=1.2 → ~12.1 s—on or over the line. EVS’s machine-tending guide puts door, chuck, and spindle-ramp overhead on the same ledger—skip “wait door” for two seconds and the paper cycle always looks pretty.

SegmentSecondsNote
Arm motion total4.8Farthest path
Door open / close wait1.5Often skipped as “the machine’s job”
Chuck / clamp handshake2.0Includes permit
Spindle / enter permit1.0Interlock
EOAT open-close0.8On the checklist
Other settle0.0–0.5Vibration-dependent
Raw≈ 10.1
×1.2≈ 12.1Compare to 12 s takt

Cycle bands and PPH (rough)

Stable cycle (with SF)Approx PPHTypical read
≤ 4 s≥ 900Very tight; path and EOAT must be clean
4–8 s450–900Common packaging / light handling band
8–15 s240–450Common machine-tending band
> 15 s< 240Heavy tooling / many handshakes—ask dual grip or split task

PPH = 3600 / cycle seconds. Before quoting shift output, confirm you used stable cycle (not demo best) and already applied SF.

Dual grippers (quantify, do not guess)

Dual grip often removes empty return trips, but tool-switch time, pose, and mass all change. Robotiq publishes formulas for the uplift—use math over “it should be twice as fast.” Dual tools also raise TCP mass and CoG; rewrite the Payload guide ledger.

Cross-constraints: cycle × EOAT × payload × reach

CrossQuestion that must share one pageRevisit
Cycle × EOATAre open-close / build-vent in the segment table? How are leak retries counted?End-effector guide
Cycle × payloadAfter full-load speed derate, is cycle still ≤ takt?Payload guide
Cycle × reach / layoutIs farthest path length based on the real base?Reach guide · Workcell layout guide

Near full load, controllers often throttle TCP speed—published notes cite on the order of 30–50% below top rated speed—so “max speed × path length” takt estimates are optimistic.

Common mistakes

MistakeFloor symptomFix
Catalog max TCP speed only4 s on paper, 7 s on floorEstimate with your path and accel
EOAT open-close skippedDemo saves 1 s+, production slipsPut beats in the list → End-effector guide
Arm motion only—waits ignoredNever matches taktAdd inspect, vent, machine overhead
Fastest loop as daily rateMisses when quality dipsLock average + slowest loop
No safety factor in the promiseMisses after handshakesApply SF 1.1–1.3 before PPH
Takt before payload / reachOverload to “make time”Validate first → Payload · Reach
Door / chuck handshakes ignoredCNC cells miss across the boardPut EVS-style overhead on one ledger

Published evidence bands

BandClaimSource
Segment sumMotion + dwell / processMFG Calcs robotics
Safety factor~1.1–1.2; complex up to 1.3FIRGELLI cycle estimator
Machine overheadDoor / chuck / ramp must enter the sumEVS machine tending
Dual-grip upliftQuantify with formulas, not gut feelRobotiq dual gripper

Common questions

How do cycle time and line takt differ?
Cycle time is real full-loop seconds (arm plus waits). Takt is the required average outbound interval. Acceptance: stable cycle (with SF) ≤ takt. Using the demo’s fastest loop to claim “under takt” is not meaningful.
What safety factor should we use?
Public estimators often cite 1.1–1.2; multi-vision or multi-machine handshakes lean toward 1.3. Start conservative; tighten only with 20–30 production loops of data—tighten with evidence, not slogans.
Can catalog max speed convert directly to takt?
No. Accel, pose, payload derate, EOAT, and waits stretch the real loop. Correct method is a segment sum—not distance ÷ max speed.
Is a dual gripper always faster?
Often for machine tending or palletizing, but switch time, pose, and mass still count. Quantify with published formulas and rewrite payload and reach.
How do we quote PPH without failing later?
Compute PPH = 3600 / seconds from the SF-inclusive stable cycle, then apply utilization (downtime, changeover, faults). Quoting theoretical PPH without stated assumptions is a common contract fight.
Takt is tight but payload / reach are not clear—what next?
Stop the promise. Overloading or hugging max reach to “make time” doubles the bill in production slowdowns or protective stops. Clear the Payload guide and Reach guide first, then lock cycle.
How do vision / vacuum retries enter the sheet?
Add an expected extra seconds term (defect rate × retry cost), or cover explicitly inside SF. Assuming “always one-shot success” pushes risk into the downstream queue.
Where should application path be narrowed if the beat sheet is still fuzzy?
Use Product Advisor to shortlist a tier, then return to the segment table with that tier’s realistic speed and payload derate—not the other way around.

Next steps

Cycle time beside three model tiers: Side-by-Side Comparison

Match payload tiers before locking the pool: Full r-Series lineup specs

Application unclear—narrow tiers first: Product Advisor

EOAT open-close still open: End-effector guide

Top view and path length: Workcell layout guide

Full-load speed derate and margin: Payload guide

Beat breakdown or station video: Contact us

Share article

New possibilities for your next cobot deployment.

Explore new ways to move your decision forward—with clarity, confidence, and less second-guessing. You don't need every detail settled before you loop in procurement or engineering. When the guides have pointed the way, the paths below help you take the next step together.