RBTXpert Debrief: Why the Spec Sheet Cycle Time Is Almost Never Your Cycle Time
Partner Resource: Epson Robots — Robot Cycle Times: Beyond the Specification Sheet
Content Type: Technical Brief
Best For: Engineers and operations managers evaluating SCARA robots for assembly, pick-and-place, or precision handling applications
Why We Are Sharing This
Every robot buyer has been there. You find a SCARA robot with a cycle time that looks perfect on paper. You quote the application around it. Then during commissioning the real-world number looks nothing like the spec sheet promised. The project timeline slips. The throughput model breaks. The business case takes a hit.
Epson’s technical brief addresses this problem directly and honestly. In our view, it is one of the cleaner pieces of vendor-produced technical content on this specific topic. It earns its place in an axis debrief for one reason: it explains something most vendors avoid saying. Their own champion cycle number came from conditions your application will almost certainly not replicate.
What the Content Actually Covers
Points, Waypoints, and Precision Tier
The brief opens with the motion path problem. A champion cycle follows a very specific path. Vendors measure it over a short distance, typically 300mm out and back with 25mm vertical movement at each end. Your application follows the path your part requires, not the path that flatters the spec sheet. The moment your waypoints change, your cycle time changes with them.
Precision tier compounds this. Epson structures its SCARA lineup across three tiers, and the tier your application needs determines how quickly the robot settles at each position. A robot placing a component for camera inspection must fully settle before the image fires. A robot dropping a part into a loose nest does not. Specifying higher precision than the application requires costs cycle time you did not need to spend.
Overshoot, Payload, and Inertia
Overshoot matters in high-speed SCARA applications. A robot that oscillates before settling loses time on every single cycle. Settle time is part of cycle time. It belongs in every pre-sale estimate, not just the motion path calculation.
Payload derating catches most buyers off guard. The rated payload is not a cliff edge. Speed derating begins before you reach the rated limit. The derating curve varies significantly between robot models. If your EOAT design puts you at 80% of rated payload, confirm exactly where that lands on the derating curve before locking in any cycle time assumption.
Inertia is the factor the brief correctly identifies as most frequently overlooked. A gripper carrying a long part applies rotational inertia to the robot’s joints that payload alone does not capture. Inertia cannot be estimated from a spec sheet. An application study calculates or measures it against your actual tooling geometry. This is where the brief’s recommendation to request an apps study becomes genuinely practical rather than a sales pitch.
Duty Cycle: Sprint vs. Sustained
The final check is duty cycle. Some robots quote peak performance that cannot run continuously. If your application runs two shifts at high cycle rates, confirm the robot’s sustained throughput. Sprint speed and production speed are different numbers. Treat them as such.
The RBTXpert Take
The most useful frame this brief provides is the distinction between a well-defined application and one still in development. Each stage demands different questions. A well-defined application can support a full application study before equipment selection. A development-stage application benefits from surfacing the key variables early, specifically precision requirements, EOAT geometry, and inertia, before those variables become commissioning surprises.
The honest content here is what earns the share. Vendors who tell you what to watch out for in their own spec sheets are worth paying attention to. This brief does exactly that. Axis recommends it as a practical pre-evaluation resource for any team comparing SCARA robots on cycle time claims alone.
Read the full Epson brief Here .
Check out Epson on RBTX Here.