Resolver 2025.4.0​

Thank you for the great turn out at both Automate in Detroit and Automatica in Munich. We enjoyed meeting all of you and hearing first hand how Resolver has substantially reduced the effort to make proposals, validate designs, and deploy robotic workcells.

In today's Resolver release

• New Connections Table
• Dynamic Cables for VC and Gemini
• PS Connector 1.2.0
• VC and Gemini Connectors 1.1.0

---

New Connections Table​

Details from the motion planning Engine

As part of the results for each run, you will see the new Connections table. The table has details about how the path segments were generated to connect one target to the next in a sequence. In the details for each robot's connections, you can find motion time, number of vias required to avoid obstacles, and interpolation type. If there were any collisions detected or interlock signals required, those are listed as well.

---

Dynamic Cables for VC and Gemini​

Support for generating paths with dynamic cables

In both VC Connector 1.1.0 and Gemini Connector 1.1.0 we have added support for exporting dynamic cables. Resolver can now take into account dynamic link attachments such as dynamic cables or simple linkage bars. Please remember to set up the correct collision detectors for the dynamic link attachments.

---

PS Connector 1.2.0​

Improvements and bug fixes

• Enable auto-tune by default
• Ensure auto-tune only uses smoothing values from import table
• Improve import of operations with tool changes
• Prevent user from changing the study while import is running
• Fix import issue when parent operation has linked device operations
• Fix various bugs in dynamics calibration
• Fix various stability issues with connector viewer
• Fix error when downloading reachability report through Connector viewer
• Additional improvements and bug fixes

---

VC and Gemini Connectors 1.1.0​

Added support for dynamic link attachments

• Add support for dynamic link attachments such as dynamic cables and simple linkage bars
• Check for missing collision detectors during export
• Fix error when downloading reachability report through connector viewer
• Additional improvements and bug fixes

---

Resolver 2025.4.0​

Component	Version
Engine	2.12.0-118-g9d55bec939
Cloud	378ddb4b
PS Connector	1.2.0
VC Connector	1.1.0
Gemini Connector	1.1.0

---

Resolver 2025.3.0​

Hallo from München. We are at Automatica 2025 (Hall B6, Booth 301) and excited to launch today two new Connectors integrating Resolver into Visual Components and MELSOFT Gemini.

In today's Resolver 2025.3.0 release

• New Visual Components Connector 1.0.2
• New Gemini Connector 1.0.2
• PS Connector 1.1.3

---

New Visual Components Connector 1.0.2​

Visual Components 4.9.2 and 4.10 supported

Download the latest version from our new Downloads page inside Resolver (log in required) at resolver.rtr.ai.
You can find more information by selecting Visual Components Connector on our documents page.

---

New Gemini Connector 1.0.2​

MELSOFT Gemini 1.48 and 1.410 supported

Download the latest version from our new Downloads page inside Resolver (log in required) at resolver.rtr.ai.
You can find more information by selecting Gemini Connector on our documents page.

---

PS Connector 1.1.3​

Improvements and bug fixes
Download the latest version from our new Downloads page within Resolver at resolver.rtr.ai. After installing the latest PS Connector, please select "RTR Resolver Viewer" from the Viewers drop-down.

The first time you log in, you will need to select your Cloud environment on the top right of the RTR Resolver Viewer depending on your location.

• Europe: Located in Europe
• Global: Americas, APAC, all other countries.

PS 1.1.3

• Improve error messages if joints exceed physical limits or working limits
• Improve error message for untaught pose locations
• Fix import issue with TeamCenter projects
• Fix issue that prevented target order optimization in some cases
• Additional improvements and bug fixes

---

Resolver 2025.3.0​

Component	Version
Engine	2.11.0-708-g661c3d6d28
Cloud	a892a0cb
PS Connector	1.1.3
VC Connector	1.0.2
Gemini Connector	1.0.2

---

Resolver 2025.2.0​

We are getting ready for Automatica in Munich, Germany and would love to meet you in person. We will have our Resolver demo as well as our RapidPlan demo in Hall B6, Booth 301. Hope to see you there!

At the same time, the team has been hard at work to bring you new capabilities including support for Material Handling and Optimize Configuration. Please remember to update your PS Connector to take advantage of all new features. Read on or review our updated documentation and tutorials at resolver.rtr.ai to learn more.

In today's Resolver 2025.2.0 release

• Support for Material Handling in PS
• Support for Stateful Objects in PS
• Optimize Configuration in PS
• UI Updates to Resolver
• Updated Documentation and Tutorials
• PS Connector 1.1.1

---

Support for Material Handling in PS​

Path planning and interlock generation for material handling

Resolver now supports operations with OLP commands used for material handling. This new capability allows you to export and upload an entire workcell with a mix of material handling and process operations.

Supported OLP commands include:

• Blank/Display
• Attach/Detach
• Grip/Release

---

Support for Stateful Objects in PS​

Account for objects, such as clamps, that change states during operations
In addition to supporting material handling, Resolver also supports operations with OLP commands that change the state of objects. If you have clamps or grippers that are actuated during an operation, Resolver will take those actions into account and generate paths and interlocks that are collision-free.

Supported OLP commands include:

• Blank/Display
• DriveDevice
• JumpDevice
• WaitDevice

---

Optimize Configuration in PS​

Why auto-teach when you can optimize the configurations?
Automatically get configurations that lead to the optimal cycle times for start/end targets as well as process points.

Start/End Targets - Optimize Tool Within Box
For start and end targets, define a bounding box that limits where the EOAT is allowed to be and Resolver will find start and end configurations that optimizes the operation. The bounding box is defined by two points relative to the TCP of the tool.

Process Targets - Optimize Tool
For process targets, Resolver can optimize the robot configuration in several ways depending on your application. Select "Optimize Configuration" to maintain the target position but find an optimal robot configuration with paths. Select "Optimize Tool Rx/Ry/Rz" to allow Resolver to rotate the target around the specified TCP axis and find the optimal configuration and paths.

---

UI Updates to Resolver​

Build UI selected automatically and new toolbar on the canvas
We continue to streamline the user interface of Resolver to help you save engineering efforts. After exporting a study, you will now be shown the Build UI automatically. Additionally, there is a new toolbar which includes a gear icon to set up the Query Settings such as "Motion Settings" and "End Conditions".

---

Updated Documentation and Tutorials​

New Tutorial videos to get you started
As we release new capabilities and features, we are constantly updating our documentation page. We have recently added a new section at the top, Tutorials, which has videos and step by step instructions to help get you started.

New Supported Features Page
For Process Simulate, there's a new section to describe the Supported Features. It includes details on what is and is not supported currently by Resolver.

---

PS Connector 1.1.1​

Added support for several OLP commands
Download the latest version from our new Downloads page within Resolver at resolver.rtr.ai. After installing the latest PS Connector, please select "RTR Resolver Viewer" from the Viewers drop-down.

The first time you log in, you will need to select your Cloud environment on the top right of the RTR Resolver Viewer depending on your location.

• Europe: Located in Europe
• Global: Americas, APAC, all other countries.

PS 1.1.1

• Add support for material handling OLP commands including Blank/Display, Attach/Detach, and Grip/Release.
• Add support for state change OLP commands including Blank/Display, DriveDevice, JumpDevice, and WaitDevice.
• Add support for tool changes during the cycle (Mount/Unmount, Connect/Disconnect)
• Add support for clearance distances between robots specified in collision sets.
• Update wording on warning messages.
• Additional improvements and bug fixes

---

Resolver 2025.2.0​

Component	Version
Engine	2.11.0-708-g661c3d6d28
Cloud	4c7d1bbd
PS Connector	1.1.1

Resolver: The Ultimate Robot Path Planner​

On Monday, May 12th, 2025 we launched Resolver at the Automate Show in Detroit, Michigan and everyone was impressed and excited about it. Some even called it the best robot demo. We could not have developed this amazing product without your input and feedback during our early access period - THANK YOU!

We launched with a ton of new features as you will see in this email, so grab some coffee and read on!

In today's Resolver 2025.1.0 release

• PS Connector integrated as a Viewer
• New cloud UI
• Target offsets
• Robot allocation
• Cartesian interpolation
• PS Connector 1.0.5

---

PS Connector integrated in PS as a Viewer​

Export directly to Resolver while you continue working in PS
Export and automatically upload, no need to deal with zip files anymore! Continue working in PS while Resolver is processing multiple options in parallel. Select your preferred results based on number of interlock zones and cycle time. Then simply import those results without leaving PS.

---

New Build UI in the cloud​

Visualize compound operations and experience new features
With the new features such as Target Offsets, Robot Allocation, and Cartesian Interpolation, we designed a new Resolver UI that is powerful, yet flexible. After exporting your study, you will see new options at the operation and target levels to fine-tune your query. Download the latest PS Connector to make sure you can access the latest UI.

---

Target Offset​

Let Resolver add approach and depart points for you
To help reduce the amount of engineering at the proposal and design stage, we are happy to introduce Target Offsets. Specify an X, Y, or Z offset with external axis values and apply it to as many points as you want, or all of them. Resolver will use the offsets as approach and depart points when path planning and generating interlocks.

---

Robot Allocation​

Optimize the target-to-robot allocation
For any multirobot application where more than one robot can perform the same task, let Resolver know which robots are allowed to be considered for that operation. Resolver will consider all robots selected and evaluate reachability, paths, and interlocks that result in the optimal target-to-robot allocation. Please note that using this feature expands the number of possible solutions and Resolver should be run longer.

---

Cartesian Interpolation​

Resolver can now plan in cartesian space to generate linear moves
Based on your feedback, we have added support for planning paths in cartesian space, when necessary. Resolver will generate paths that are based on linear moves if possible. If there are collisions or too many singularities, it will revert back to joint space. The interpolation type must be specified in the cloud UI since we are not yet collecting the data directly from PS. This feature is coming soon to the PS Connector.

---

PS Connector​

Our first official Public Release!
Download the latest version from our new Downloads page within Resolver at resolver.rtr.ai. After installing the latest PS Connector, please select "RTR Resolver Viewer" from the Viewers drop-down.

The first time you log in, you will need to select your Cloud environment on the top right of the RTR Resolver Viewer depending on your location.

• Europe: Located in Europe
• Global: Americas, APAC, all other countries.

PS 1.0.5

• Add RTR Resolver Viewer to replace the previous export and import dialogs
• Significantly reduce overall wait times and speedup entire workflow
• Project configuration in Resolver cloud can be done while the project is still exporting
• Add support for dynamic link attachments such as dynamic cables and simple linkage bars
• Update signal handling for interlocks using Signal Manager
• Additional improvements and bug fixes

---

Resolver 2025.1.0​

Component	Version
Engine	2.11.0-472-gf1d95c3c9c
Cloud	50667afe
PS Connector	1.0.5

Resolver Update​

With only 12 days until the official Resolver Launch, we continue to add more features and capabilities that you have requested. We are also excited to share our revamped website. Come take a look!

Today's update:

• New Results Preview
• New Downloads page
• PS Connector 0.14.1-beta released

---

Results Preview​

Playback the latest results
Now you can finally see how your run is going before it completes. To use the new Results Preview, simply click on Get Current Results to load the latest data, then expand the Results Preview window and watch a simulation of the generated paths and interlocks.

---

Downloads Page​

Integrated into Resolver
On the lower left hand of the Resolver Cloud you will find the link to the Downloads page.

Within the Downloads page, you can download the default, or latest, connector for each simulation tool. We will be adding more items in the coming weeks.

---

PS Connector​

Improvements and bug fixes
Download the latest version from our new Downloads page within Resolver!

PS 0.14.1-beta

• Add support for "joint working limits," shrinking the joint limits based on the PS setting
• Speedup export by reducing number of API calls to get joints
• Improve algorithm for exporting objects based on collision sets, resulting in quicker project loading
• Improvements to AutoTune
• Fix configuration mismatch when importing a custom TCP
• Disable reach advisor during simulation in export/import
• New warnings and fix issues with export and import

---

Resolver Update​

We have some improvements and bug fixes for our PS Connector this week. We are committed to getting the latest software to you as quickly as possible.

Today's update:

• PS Connector 0.13.1-beta released

---

PS Connector​

Improvements and bug fixes
Download the newest version from Optimized Path Planning Beta folder from the RTR FileShare.

PS 0.13.1-beta

• Improve error message about joint being controlled by multiple robots
• Silence exceptions about unsolvable kinematic loops
• Fix export error with X-type guns
• Fix export error when multiple kinematic loops start at a single node
• Fix export error when robot controllers were changed
• Fix various export issues with coupled joints and dependent joints
• Fix locale dependent floating point conversion
• Fix incorrect external axis values if no external axis value is specified for a target

---

Resolver Update​

We continue to work on the challenges we shared previously. This week we added a warning to the PS Connector if a robot does not have self-collision sets defined. Self collisions include tool-to-robot, robot-to-RTU, and tool-to-RTU. Thank you for your continued support and feedback.

Today's update:

• PS Connector 0.12.0-beta released

---

PS Connector​

Self-collision Checks
Download the newest version from Optimized Path Planning Beta folder from the RTR FileShare.

PS 0.12.0-beta

• Add warning for robots without self collision sets during export
• Disable OLP commands during calibration and AutoTune
• Bug fixes for external axes, error messages, and more.

---

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.

🎁 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.

🎁 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.

---

Resolver Update​

We're excited to introduce an upgrade to Resolver's PS Connector—now with enhanced smoothing value selection for motion generation. At the same time, we recognize, based on your invaluable feedback, that there are areas where we need to improve. Below we share with you what the challenges are and what we are doing.

Today's update:

• Challenges we are working on
• Robot vendor-specific smoothing
• PS Connector 0.10.0-beta released

---

Challenges we are working on​

The performance of some features are not up to our standard
As we continue to innovate and quickly bring new capabilities to help you reduce engineering time, some of the capabilities and features are not delivering the value you have come to expect. As a result, we wanted to let you know we are working to make drastic improvements in the following areas:

Auto-tunning on Import
Issue: Auto-tuning on import with RCS can take minutes to several hours to complete.

What we are doing: We are making the import code faster, introducing fast and optimal tuning options, and allowing the user to set the simulation time interval. We expect these features to be ready shortly.

What this means for you:

• If simulating without RCS, please use auto-tuning. It will take a few minutes.
• If using RCS, know that auto-tuning could take several hours. In the short term, importing without auto-tuning and manually touching up collisions is also an option.

Self-collisions of robots
Issue: We have reports of self-collisions of robots and attachments. The reason for this issue is that no collision rules have been defined. Examples include 1) collisions between a weld gun and the robot and 2) collisions between the weld gun and RTU. Please read the Collision Rules section of the docs for more information.

What we are doing: We are exploring different options to simplify the workflow and validate expected collision sets.

What this means for you:

• Ensure collision sets are defined between robot links and any attachment to the robot.

Optimize Tool Configuration in Rx, Ry, or Rz
Issue: The Optimize Rz functionality is producing sub-optimal results for spot weld applications when targets have robot to part collisions. This happens frequently because the engine is not currently aware that the gun tips can be ignored. Work has already been done to encode ignore collision rules at the targets for the gun tips, but some engine work remains.

What we are doing: We will be disabling this feature in the coming days until the gun tips are properly defined and dealt with in the engine during TCP orientation optimization.

What it means for you:

• If you have an opportunity to optimize the tool rotation, try running both with and without the Optimize Rx, Ry or Rz.

---

Robot Vendor-Specific Smoothing​

Previously, users could only specify 5 (mm) smoothing values. Now, we've expanded support to include all Robot-specific smoothing options by default, giving you greater flexibility and control. Simply deselect any options you don't need!

Please note: The FINE option cannot be unchecked because it is required for interlocking at newly generated via locations.

This improvement was driven by your feedback—and we're thrilled to turn another user request into reality. Please let us know what you think!

---

PS Connector​

New controller-specific smoothing values
Download the newest version from Optimized Path Planning Beta folder from the RTR FileShare.

PS 0.10.0-beta

• Added robot vendor specific smoothing values to exporter.
• Add logging of diagnostics data for export and import.
• Additional warnings for stationary tools, large joint limits. etc.
• Bug fixes in interlocks, target locations, smoothing conversion.

---

Resolver Update​

In this latest release, we have added a feature that empowers you with data to make better decisions. Resolver now generates several solutions with less number of interlocks and corresponding cycle times to let you pick the one that best fits your project needs.

Today's update:

• Interlock Reduction

---

Interlock Reduction​

New post-processing step to reduce interlock zones!
We're excited to introduce automatic interlock post-processing in Resolver. Once you accept the results and stop a run (not current results), the Engine will intelligently consolidate interlock zones—without altering robot motion paths.

The output will include all possible interlock reduction options, along with a cycle_times.yaml file (see image below) detailing estimated cycle times for each result. You can then select which results file to import back to your simulation.

As always, we value your feedback—let us know how this feature works for you!

---