Skip to main content

Import Results

Importing Results from Resolver Cloud​

After successfully completing a run in Resolver, one or more [results].yaml files will be generated inside a .zip file.

Inside the .zip, you will find both Sequential InterlockRobots exchange release signals once they reach a certain point in the sequence. Interlocks are not areas that robots can reserve in any order but fixed positions where specific robots must wait until... and Spatial InterlockA spatial interlock is used between two robots that share the same space. To prevent collisions, a signal is used to indicate that a robot is in the zone. There is no priority given to either robot -... results. There may be multiple Spatial Interlock results depending on the project.

Choosing an Interlock Count​

Each result is the same motion plan with a different number of interlocks. More interlocks generally means a shorter cycle time, because the robots are allowed to work closer together in time — but every interlock is a coordination constraint your controllers have to enforce on the floor.

Open cycle_times.yaml in the results .zip to see the cycle time for each count, then pick the lowest count that meets your target cycle time rather than the highest count available.

Before You Begin​

Ensure the same study used for the export process is open in Visual Components.

In VC Connector 1.24.0 and later, the connector also checks the study before an import starts and reports any of these problems:

  • A robot is missing from the layout.
  • An interlock robot is missing.
  • An interlock has no signal.
  • The simulation has not been reset.
  • A reference routine is missing.
  • A motion type has changed.

Fix what the check reports, then run the import again.

There are two ways to import results — Online and Offline:

Online Import​

  1. In the Realtime Robotics Connector, open the Resolver tab, find the completed run, and click Download Results.

    Connector Resolver tab with the Download Results button highlighted

  2. Select the interlock type and count, then click Import.

    Import panel listing each result with its estimated cycle time and interlock count

  3. The optimized sequence(s) will be automatically added to all applicable robots.

note

If only one robot sequence was exported, only that robot will receive an optimized path.

Offline Import​

Make sure Automatically Connect to the Cloud is toggled off in Settings to enable importing from a local file.

You import the results archive exactly as it downloaded from Resolver:

The downloaded results archive listed in Explorer, with its Type shown as Compressed (zipped)
Import the archive as downloaded — Explorer shows its Type as Compressed (zipped).

  1. In the import dialog, click Browse and select that .zip. Do not unzip it first.

  2. Choose which result to import — sequential or spatial reduced — and select the number of interlocks, as described in Choosing an Interlock Count above.

    Connector Import tab with the selected result archive and the list of results to import

note

The file picker is titled Import RTR Zip... and accepts .zip only. Selecting a loose .yaml is a developer-only option and is not available in a normal installation.

After Import​

Once the import is complete:

  • In the Visual Components Program Editor, the new Resolver-generated path sequence will be visible.
  • Add this imported sequence to your main sequence to integrate it.
  • Press Play to review the optimized, collision-free motion paths created by Resolver.

Validate the Result​

Before you take the paths further, confirm all three:

  • Every robot you exported received a sequence. If one did not, check that it was included in the export and that it had an operation.
  • Playback is collision-free. Run the simulation through a full cycle with your collision sets enabled.
  • The cycle time matches Resolver's estimate. A large discrepancy usually means the imported sequence is not the one being played, or it has not been added to the main sequence.

If the Import Fails​

  • Nothing to import, or the wrong targets appear — the open study is not the one you exported. Open the original study and import again.
  • The file picker rejects your file — it accepts .zip only. Import the archive exactly as downloaded from Resolver; do not unzip it first.
  • The import hangs on a spatial-interlock result — this was fixed in Connector 1.22.0. Check your version with ☰ → About... and update if you are older.

For anything else, take ☰ → Save Logs and attach the logs to a support ticket.

Your optimized results are now live in your Visual Components study. If you want to try a different interlock count or adjust the run, go back to Configure in Resolver and start a new run.