Skip to main content

Objects not included in Collision Sets

Error ID: 3103
Platform: Process Simulate

This sanity check identifies objects that are used in operations but are not included in any collision sets. These objects will not be checked for collisions during path optimization, which may lead to collision issues in the optimized paths. This is a warning only; export can proceed, but the user should consider adding these objects to collision sets.

What this error means​

  • Severity: Warning
  • Blocking behaviour: informational_only
  • Dialog type: Warning - Informational only (OnlyWarning)
  • 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​

Operation: {operationName1}, {operationName2}
Object: {objectName}

Objects referenced in operations but not included in collision sets
Add objects to collision set for accurate collision detection

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. If this message is informational or a warning, you may be able to continue, but it is recommended to fix the underlying issue early to avoid problems later in the workflow.
  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.