Skip to main content

Large joint limits

Error ID: 2101
Platform: Process Simulate

This sanity check detects joints with unusually large range limits. For revolute joints, limits exceeding 4 complete rotations (1440° or ~25 radians) are flagged. For prismatic joints, limits exceeding 100 meters are flagged. Such large limits often indicate modeling errors or misconfiguration and can cause optimization issues. The user can review and fix the joint limits or proceed with the export.

What this error means​

  • Severity: Warning
  • Blocking behaviour: allow_cancel
  • Dialog type: Warning - Can continue or cancel (AllowCancel)
  • The message indicates that Resolver found an issue with the current Process Simulate setup and is warning you before continuing with the export/import workflow.

Dialog text shown in Resolver​

Robot: {robotName}
Joint: {jointName}

Rotation limit range exceeds 4 complete turns
Index: {index}, Range: {min}, {max}

Verify joint limits

How to fix it (step-by-step)​

  1. Carefully read the dialog text shown above and note any robots, operations, objects, or settings that are mentioned.
  2. In Process Simulate, inspect the affected station or operation and verify that the setup matches the expectations described in the message (for example: targets, robots, kinematics, collision sets, RCS configuration, export options, cloud settings, etc.).
  3. Decide whether it is safe to continue based on your project phase. If in doubt, cancel the operation, fix the root cause in Process Simulate, and then retry.
  4. Save your changes in Process Simulate and run the Resolver import/export again.
  5. Confirm that the message no longer appears, or that it now reflects the updated configuration correctly.

When is it safe to ignore this warning?​

You may choose to continue without fixing this issue when:

  • you are running a quick test or proof-of-concept,
  • the affected configuration does not impact the robots or operations you care about,
  • you fully understand the implications described in the dialog.

For production use, it is strongly recommended to resolve the cause of the warning rather than ignoring it.