Skip to main content

No RCS available

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.

Dialog shown in Resolver​

{rcsError} RCS is unavailableImported trajectories might not be collision-free Continue with MOP?

What you can do in this dialog​

  • Can you continue export? Depends on your choice
  • Buttons in the popup: Yes, No
  • What happens next: Yes continues. No cancels/stops the current export flow.
  • Next step: See impact if you continue

Impact if you continue​

Choosing Yes finishes import using MOP while auto-tune cannot rely on RCS for clearance-aware tuning. Imported trajectories are not guaranteed collision-free until you validate them in Process Simulate.

How to fix it​

  1. Read the {rcsError} line in the dialog for the underlying RCS failure (connection, license, instance, configuration).
  2. Restore RCS availability—connect the controller, start the RCS service or correct robot RCS selection in Process Simulate—then retry import with RCS online.
  3. If you cannot restore RCS immediately, choose No and disable auto-tune for that import, or accept Yes knowing paths were not tuned with RCS and need re-validation before you rely on them.