Skip to main content

CW13 Update

· 3 min read

Resolver Update

In the last update we shared with you some challenges we have been working through. We are happy to announce that we made drastic improvements to the Auto-Tuning of smoothing values on Import. We are also happy to release a downloadable Reachability Report which details the ability of individual robots to reach assigned targets.

Today's update:

  • Auto-tuning on Import
  • Reachability Report
  • PS Connector 0.11.0-beta released

Auto-Tuning on Import

Smoothing Auto-tuning in minutes!
In our previous release, we acknowledged performance limitations with the auto-tuning of smoothing parameters during import. Since then, our team has been hard at work—and we're excited to share the results.

With this release, we're introducing significant improvements to API efficiency and two powerful new import modes: FAST and OPTIMAL.

FAST Mode

Need speed? FAST mode quickly imports paths using default conversion values tailored to your selected robot OEM. If scraping collisions are detected, it smartly adjusts to a FINE smoothing level. This mode is ideal for rapid validation when your priority is speed—just note that in high-collision scenarios, some smoothing may be less than ideal.

OPTIMAL Mode

Looking for precision? OPTIMAL mode performs an in-depth analysis to find the highest possible smoothing value for each via—based on your allowed values—delivered through our Resolver engine. We've reengineered the API interactions behind the scenes, significantly reducing optimization time while delivering the highest-quality path smoothing available. While the time required still scales with the number of smoothing options per via, the results speak for themselves: ultra-smooth, OEM-optimized paths.

cycle_times.yaml

🎁 Solution delivered for Roland and Rico


Reachability Report

Quickly check check reachability of all targets and download report Manually jumping robots to each target only provides limited reachability information and is also so boring. Now you can save a ton of engineering time by letting Resolver do the reachability check for you. Resolver will check if robots are able to reach their assigned targets by generating actual motion paths. In minutes it will put the information in a nice table that can be downloaded in CSV format for you to use elsewhere in your planning and engineering processes.

The different states displayed on the table are:

  • Pending (hourglass): the Engine is calculating reachability.
  • Not Reachable (red): the target is not reachable.
  • In Collision (yellow): the target is reachable but only through a collision.
  • Reachable (green): the target is reachable without collision.

cycle_times.yaml

🎁 Solution delivered for David


PS Connector

Improvements to Auto-tune
Download the newest version from Optimized Path Planning Beta folder from the RTR FileShare.

PS 0.11.0-beta

  • Auto-tune improvements and addition of two modes (fast & optimal mode)
  • Updated installer to allow installation without admin privileges if current user has sufficient rights (thank you Pawel for the suggestion!)
  • Added support for SCARA robots
  • Additional warnings for stationary tools, large joint limits. etc.
  • Bug fixes for external axes, error messages, safety objects, and more.