Why Does IRB 5720 MultiMove Show Configuration Not Supported?

No motor current flows and no thermal or motion-timing limit is involved at this stage; RobotStudio rejects the system while validating its configuration. The red configuration not supported result means the selected IRB 5720 mechanism, controller family, RW version, options, and two-robot arrangement do not form a supported virtual-controller definition. Because the same workflow accepts two IRB6700 robots, station position is not the primary fault; check the IRB 5720 controller and MultiMove compatibility boundary first.

Meaning of the Configuration Symptom

The failure occurs after selecting the RW version in Virtual Controller from Layout, before RobotStudio creates the controller. That timing separates a configuration-validation problem from a kinematic, collision, electrical, or communications problem. Moving either robot, changing its base coordinates, or modifying a motion path cannot correct a system definition that the controller builder rejects.

The number that matters is the mechanism count: one IRB 5720 tests basic robot-to-controller compatibility, while two test the added MultiMove requirement. Run both cases. If one robot fails, investigate the robot model, controller family, and RW pairing. If one succeeds but two fail, the incompatibility is specifically introduced by the multi-robot architecture or its required option set.

Robot Model and Controller Separation

A RobotStudio library component provides the simulated mechanism: geometry, joints, limits, mounting data, and related model metadata. Loading ABB\RobotStudio2022\Packages\ABB.RobotStudio.Models.IRB5720-1.4\RobotStudio\LibraryComponents can therefore make IRB 5720_125_300 available in the station without proving that the selected virtual controller can operate that mechanism in a MultiMove system.

Controller creation performs a second validation. It must match the robot mechanism to a controller family, an installed RW package, a supported robot definition, the requested number of mechanisms, and the necessary system capabilities. A valid graphical model can fail this test.

If the IRB 5720 selection resolves to an OmniCore controller, verify whether that controller and the selected RW release expose MultiMove for this robot combination. OmniCore is a decision point to check, not a conclusion to infer from the model folder. Read the installed product metadata and ABB compatibility documentation for the exact controller-and-release pairing.

Diagnostic Quantities and Decision Points

Also record whether the builder exposes a MultiMove-related capability for the proposed system. A missing capability, a controller-family restriction, or an unavailable robot mapping can produce the same red validation mark. The displayed error is broad, so the one-robot/two-robot split is the fastest way to localize it.

Controlled Reconstruction Procedure

1. Create a clean test station and add one IRB 5720_125_300 from the identified library component. Keep tooling, external axes, and application logic out of this first test so they cannot add another compatibility variable.
2. Run Virtual Controller from Layout with the same RW version used in the failing station. Record the proposed controller family and whether the configuration page accepts the single mechanism.
3. If the single-robot case fails, stop treating MultiMove as the root cause. Compare the model package, installed controller software, controller family, and robot support metadata. Align the installed packages only with a combination listed as supported by ABB.
4. If the single-robot case succeeds, add the second identical IRB 5720 and repeat controller creation without changing the RW version. A failure introduced at this step isolates the two-robot capability or option set.
5. Inspect the proposed controller family. If RobotStudio maps the IRB 5720 system to OmniCore, check the official compatibility and option information for MultiMove on that controller and selected RW release.
6. Repeat the two-IRB6700 control test using the same controller-creation workflow and, where selectable, the same RW version. This confirms that the installation can build a multi-robot system while keeping the robot family as the changed variable.
7. Create the final virtual controller only from a published-supported robot, controller, software, and option combination. If no supported IRB 5720 MultiMove combination is listed, use a different supported architecture rather than attempting to bypass the validation.

Verification of the Result

A corrected configuration must pass more than the page containing the red mark. Confirm that RobotStudio completes virtual-controller generation, starts the controller without a configuration rejection, and associates both intended mechanisms with the generated system. Then confirm that the requested MultiMove capability is present in the system definition rather than assuming that two visible robot models imply coordinated control.

Save, close, and reopen the station, then start the virtual controller again. This detects a temporary layout state or unresolved package reference. After controller startup succeeds, command limited simulated motion for each mechanism and confirm that the controller addresses the intended robot. Collision checking and coordinated-path behavior are later tests; they cannot validate an unsupported controller definition.

Recurring Configuration Pitfalls

The most common error is treating a component copied from LibraryComponents as a complete controller-support package. It proves that RobotStudio can draw and articulate the mechanism. It does not prove that every installed RW release or controller family can create a system for it.

Another trap is changing robot positions to clear the warning. Layout coordinates affect reach, overlap, and collision behavior after controller creation; they do not add a missing controller capability. Likewise, success with two IRB6700 robots validates the procedure and installation path only. Robot families can have different controller mappings and supported option combinations.

Avoid cycling through RW versions until the red mark disappears without checking compatibility data. An accepted build must still correspond to the controller and software intended for deployment. Record the exact selected version and controller family so the virtual system can be compared with the target design and reproduced.

Frequently Asked Questions