Currently, no. Each tool requires a separate cell configuration

Through the linkage in the imported data—each sequence is assigned to a robot in the configuration files.

One robot can currently only handle one sequence per operation. Multiple robots each need their own defined sequence.

Accurate collision sets, robot configurations, tool setups, and motion start/end points.

If properly configured and using RCS, results are close to real-world behavior. Without RCS or proper dynamic parameters, results can vary.

Yes, for realism—especially for checking collisions, path planning, and actual cycle times.

KUKA, ABB, and FANUC* are most relevant for German OEMs and supported well by Resolver.

Please know - currently the CNT values provided by Resolver might not ensure CNT100 can be used in the majority of the via locations. Our team is working to allow CNT100 values in the majority of the via locations.

This happens when the path is exported in one station position (e.g., Rotation) but imported while the station is in another (e.g., Loading). Resolver does not auto-adjust for mismatched states.  Always import paths using the same station configuration used during export. This is a usage error, not a software bug, and doesn’t affect functionality.

This can happen if the stationary gun is closed during export. Resolver requires the gun to be in an open state to avoid collisions and properly calculate optimized paths. Before exporting your operation Process Simulate, ensure the stationary gun is open. This allows Resolver to simulate robot movement without collision errors.

Note:  If the gun state changes between export and playback (e.g., Resolver used an open gun but the playback uses a closed one), collisions may still occur. A fix is planned in a future version, but for now, keep stationary guns open during export to avoid issues.

You can download the latest version of the PS Connector from the Realtime Robotics FileShare. If you don't have access yet, register with your email, then notify your RTR support contact to gain access to the required folders.

We are transitioning from FileShare. A new dedicated Downloads page is added to the Resolver platform. Connectors for simulation tools (e.g., Process Simulate, Visual Components) can be downloaded from here. Demo studies will also be available for users to try out in a sandbox environment.
Legacy versions of connectors will remain available temporarily for backwards compatibility.

Register on the FileShare platform using your email. After registration, let your RTR support contact know so the necessary folders can be made available to your account.

The recommended method is using the Windows Installer . It's the easiest and most reliable option.

If the Windows Installer fails, you can use the Legacy Installation Process. This involves manually copying DLL files into the appropriate Process Simulate folders.

Right-click the top banner in Process Simulate and select “Customize the Ribbon…” . Then, add the Export to RTRand Import from RTRcommands to the Robot -> Realtime Roboticstab.

The Windows Installer installs in the Tecnomatix folder,  by default in C:\Program Files. If using the legacy process, DLL files go into your DotNetCommandsfolder, and the XML config goes into DotNetExternalApplications. Paths may vary based on your environment.

Open Process Simulate and click the Export to RTR button on the ribbon. A dialog box will appear displaying your PS Connector version. This confirms installation.

Right-click the ZIP file, select Properties , and check for an 'Unblock' option. If visible, check the box and click OK. This step may require admin rights.

If your version is not available, it may not yet be supported. Contact your RTR support contact to report the issue—we'll investigate further.

Only the objects visible at the time of export in Process Simulate are included in the exported .zip. We recommend blanking any unnecessary entities to reduce file size, improve resolver performance, and avoid errors related to unsupported objects.

Robots without operations will be exported at their current positions as static obstacles.

Very important! Collision sets defined in Process Simulate translate directly into collision_rules the Resolver project.yaml. Poorly defined or missing collision sets can result in unexpected or incorrect motion paths.

If your collision set includes process points, set the Near Miss value to less than 2mm . Higher values ​​can dramatically increase planning time. Use larger values ​​only for standalone objects (eg, pillars) where a wide clearance is needed.

Resolver currently supports point to point applications, such as:

• Spot welding 

• Stud welding

• Riveting

• Inspection

• Material Handling (Q2 2025)

Other applications may be supported upon request. Please contact our support team to discuss your use case.

The robot controller you select at the time of export is used for Dynamics Calibration . To ensure accurate cycle time predictions, make sure to use the same controller when reviewing results in Resolver. Always choose an RCS controller if available.

MOP does not synchronize joints by default. To match Resolver's path predictions, ensure the following line is added to your robot controller's motionparameters.efile:

nginx

CopyEdit

single_joint_prof single_prof

Currently, one operation per robot is supported in a resolver export. All operations start at the same time and execute in parallel.

Only include targets the robot must reach , such as process points and essential vias.

Resolver will generate optimized motion between them. Ensure all targets are fully configured—run Auto-Teach if needed before exporting.

A fully prepared cell ensures alignment between physical reality and simulation. This includes correct layout, robot backup programs, and RCS module configuration, all of which are essential for accurate planning and path optimization.

• Latest backup programs from the robot (if existing cell)

• Finalized cell layout (ideally identical to what’s deployed)

• Correct sequence names and order

• RCS module set up properly

• Display and Blank OLP Commands included
  
  

• Ensure the cell is simulation-ready and approved

• Clearly define the robot(s) and sequence(s) involved

• Use accurate and cleaned-up sequences

• Communicate your final approval for us to begin optimization
  
  

Once export is complete, upload the .zipto Resolver Cloud to begin the motion planning process.