Mech-Viz Release Notes

You are currently viewing the documentation for the latest version (2.2.2). To access a different version, click the "Switch version" button located in the upper-right corner of the page.

■ If you are not sure which version of the product you are currently using, please feel free to contact Mech-Mind Technical Support.

Mech-Viz 2.2.2 Release Notes

This section introduces the new features and resolved issues of Mech-Viz 2.2.2.

New Features

Support for Changing the Runtime Data Path

Mech-Viz 2.2.2 supports changing the runtime data path. By default, runtime data is saved in the root directory of the software installation directory. If you do not have write permission for the installation directory, go to Options Advanced Runtime Data Settings to change where runtime data is saved. This prevents runtime data from failing to save due to insufficient permissions while the software is running.

For changes to other resource storage paths related to this feature, see Upgrade Notes.

Support for Setting Imported Scene Models as Bins

Mech-Viz 2.2.2 supports setting imported scene models as bins and specifying the bin opening position and picking range. After the settings are configured:

The Smart Path in Bin Step can plan paths for the robot to enter and exit the bin based on bin information.
The Vision Move Step can filter picking points based on the picking range.

Before using this feature, configure an available collision model for the scene model.

Support for ABB PoWa Robots

Mech-Viz 2.2.2 adds support for ABB PoWa robots, which can be used for motion simulation and path planning with these robots.

Resolved Issues

Mech-Viz 2.2.2 resolves the following issues:

When the "Vision Move (Trajectory)" Step was used to execute a trajectory, the actual motion velocity did not match the velocity set in the plan.
Some move-type Steps incorrectly marked path points as unreachable when the poses in the vision results had not yet been determined.
When teaching a target object pose through standard interface communication, the robot pose might change in the 3D simulation space.
An invalid pose in the vision results was treated as the default pose for path planning, resulting in an incorrect path point.
Point cloud collisions were occasionally not detected during picking simulation.
During picking simulation, the set rotation angle around the Z-axis did not take effect after a target object placement orientation was set.
In ordered multi-bin picking simulation, subsequent bins reused the random target object rotation angle of the first bin.
The exit point planned by the "Smart Path in Bin" Step might be below the bin rim.
A submodel might be lost after editing an existing scene object and repeatedly changing its type.
The intrinsic parameters and image resolution of the LSR L-GL camera model differed from those of other models in the same series.