Skip to main content

No RCS available

Error ID: 2105
Platform: Process Simulate

This message appears when attempting to import with auto-tune enabled but RCS is not available. Since RTR Resolver relies on RCS for accurate path tuning to prevent collisions, proceeding with MOP may result in path collisions. The user can choose to continue at their own risk or cancel to enable RCS first.

What this error means​

  • Severity: Warning
  • Blocking behaviour: question
  • Dialog type: Warning (Yes/No buttons)
  • 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​

{rcsError}

RCS is unavailable
Imported trajectories might not be collision-free

Continue with MOP?

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.