Robotics & Automation worked example

Robot Reach Margin with rated robot reach of 180 in: a worked example

What does the result look like when rated robot reach reaches 180 in? The full calculation is worked below with real intermediate numbers. Use it during layout review when the robot, fixtures, and conveyor are not yet committed and you need to confirm the farthest TCP point sits inside the reach envelope.

The inputs for this scenario

  • Rated robot reach (max envelope): 180 in (raised for this scenario; the documented default is 71)
  • Farthest required TCP point: 66 in (unchanged)
  • Reference reach for percent basis: 71 in (unchanged)

Working through the calculation

  • Applying the documented formula (Reach margin = rated robot reach - farthest required TCP point) to the inputs above produces each figure below.
  • At this operating point the engine returns 114 in margin for reach margin, the number this scenario is built around.
  • At this operating point the engine returns 161 % for reach margin percent.
  • At this operating point the engine returns 180 value for rated robot reach.
  • At this operating point the engine returns 66 value for farthest required tcp point.

How this compares with the baseline

  • Against the tool's baseline example, where rated robot reach sits at 71 in and the headline result is 5 in margin, this scenario comes in 2,180% above the baseline at 114 in margin.
  • A figure at this level is achievable when rated robot reach is genuinely sustained, not just peaked for a shift. It treats reach as a single straight-line distance and ignores wrist orientation, gripper offset, and joint limits, so a positive margin does not guarantee a reachable pose at every point.

Results at a glance

  • Reach margin: 114 in margin (headline result)
  • Reach margin percent: 161 %
  • Rated robot reach: 180 value
  • Farthest required TCP point: 66 value

Run it with your numbers

  • Every input above is editable in the live Robot Reach Margin calculator, which recalculates instantly and can be shared with the inputs intact.

Last reviewed 2026-05-12.