PolyScope 3.7: A Dependency Mismatch, Not a Bad URP

A .urp program that opens in PolyScope 3.6 but crashes PolyScope 3.7 is most likely reaching a missing or mismatched program dependency during deserialization, not failing because of its 12.3 KB file size. Load the correct default.installation in 3.7 and install the required Robotiq URCap before opening B_050_058_370.urp. Test each dependency separately so the result identifies the failing layer.

Version-Bound Loading Symptom

The number that matters is the first software version that fails: the same program opens in 3.6 and fails during loading in 3.7. That boundary directs troubleshooting toward the 3.7 runtime environment, its installation context, or its URCap compatibility rather than toward program size or robot motion.

A .urp file is not necessarily self-contained. Its program tree can refer to configuration held in an installation file and to node types supplied by URCaps. PolyScope must reconstruct those objects while opening the program. If 3.7 cannot resolve or initialize one of them, the failure can occur before the program tree becomes available for editing.

Load-Time Dependency Mechanism

This is object reconstruction, not robot logic execution. When PolyScope opens a saved program, it reads the serialized program tree, associates it with an installation, and asks installed extensions to recreate their program nodes. A program may therefore load on the environment where it was created but fail on another environment that lacks the same installation data or extension.

The installation supplies configuration outside the visible sequence of moves and commands. An incorrect installation can leave referenced resources unavailable or change the context in which a contributed node initializes. Loading the proper default.installation before opening the program gives PolyScope the expected configuration context.

The Robotiq URCap supplies software objects used by Robotiq-specific program nodes. Without that URCap, PolyScope 3.7 may encounter a node type it cannot construct. An installed but incompatible URCap can cause a similar load-time failure because presence alone does not prove that the extension initializes correctly under the target PolyScope release.

Dependency Isolation Checks

Start with a controlled comparison between the working 3.6 environment and the failing 3.7 environment. Record the active installation and the installed Robotiq URCap in each environment. Compare actual selections and installed components rather than relying on matching file names alone.

1. Confirm that the untouched B_050_058_370.urp still opens under PolyScope 3.6. This separates an environment problem from later file corruption.
2. In PolyScope 3.7, identify the currently loaded installation before opening the program.
3. Check whether the required Robotiq URCap appears in the installed URCaps list and whether it initializes without an extension error.
4. Review any diagnostic message or log produced at the instant of the 3.7 crash. The useful entry is the first failure associated with program parsing, installation loading, or URCap initialization; later shutdown messages are consequences.
5. Open a simple program created directly in 3.7. If that also fails, troubleshoot the 3.7 installation itself before analyzing this program.

Preserve the original program and installation files throughout the test. A copy provides a fixed baseline and prevents a save operation in the target version from changing the only known working artifact.

Controlled Recovery Procedure

Change one dependency at a time. If the installation and URCap are introduced together, a successful load proves that the environment was repaired but does not reveal which dependency caused the crash.

1. Back up the working 3.6 program and its associated installation data while the robot is available. Keep B_050_058_370.urp unchanged.
2. Start PolyScope 3.7 without opening the affected program automatically.
3. Load the proper default.installation in 3.7.
4. Close and reopen the affected .urp file. If it loads, record the active installation as the decisive change.
5. If it still crashes, install the missing Robotiq URCap required by the program. Use the URCap package approved for the target PolyScope environment; read its compatibility information rather than inferring compatibility from its name.
6. Restart PolyScope if the URCap installation workflow requests it, then confirm that the extension appears as installed and initializes normally.
7. Open the same untouched B_050_058_370.urp again under 3.7.
8. If the crash remains, capture the 3.7 diagnostics and compare the program dependencies against the working 3.6 environment. The first unresolved class, installation reference, or extension initialization failure determines the next action.

For a robot operating continuously, carry out the migration during a controlled maintenance window or in an equivalent offline PolyScope environment first. A program-loading test does not require releasing motion, but changing the active installation on production equipment can alter configuration used when execution resumes.

Post-Load Verification

A successful editor opening is only the first acceptance condition. Confirm that the complete program tree appears and that Robotiq-contributed nodes are present rather than replaced, blank, or marked unresolved. Open the installation view and verify that the intended default.installation remains active.

1. Navigate through every branch containing Robotiq nodes and check that each node opens without an error.
2. Save a working copy under a new name, close it, and reopen it in 3.7. This tests both serialization and deserialization in the target version.
3. Restart PolyScope 3.7 and reopen the saved copy again. This exposes dependencies that were available only in the initial session.
4. Review the program for unresolved nodes or missing configuration before enabling execution.
5. Apply the site’s normal validation process before returning the robot to automatic operation.

The deciding result is repeatable loading after a clean restart with the intended installation and Robotiq URCap active. One successful opening without a restart can hide a transient session state.

Recurring Migration Pitfalls

Frequently Asked Questions