Mech-Viz Release Notes

You are currently viewing the documentation for the latest version (2.2.0). 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.0 Release Notes

This section introduces the new features, improvements, and resolved issues of Mech-Viz 2.2.0.

New Features

Added Picking Simulation Feature

Mech-Viz 2.2.0 added the Picking Simulation Tool to verify robot picking schemes in a virtual environment.

Added "Vision Move (Trajectory)" Step

Mech-Viz 2.2.0 added the Vision Move (Trajectory) Step, which can plan robot trajectories according to vision results returned by vision projects. It can be used for scenarios such as gluing and grinding.

Support for Target Object Library Integration When Configuring Bins

In Mech-Viz 2.2.0, when configuring bins, you can use bins already configured in the target object library.

Improvements

Enhanced Sample Projects

Mech-Viz 2.2.0 added the following sample projects:

Group Sample Project Name

Others

Picking Simulation Validation, Wheel Hub Edge Grinding

Enhanced Solution Saving Path Protection Mechanism

Mech-Viz 2.2.0 enhanced the solution saving path protection mechanism, prohibiting saving solutions to system disk folders or desktop to reduce the risk of system file corruption due to misoperation.

Removed Functionality from Some Steps

Step Improvement Details

Visual Move

The "One-time completion of all vision poses" feature is no longer supported in the "Global vision result configuration" of the Vision Move Step. It is recommended to use the new Vision Move (Trajectory) Step to implement related functionality.

Trigger at Fixed Point, Relative Move

The "Collision Avoidance" feature is no longer supported in the "Trigger at Fixed Point" and "Relative Move" Steps.

Resolved Issues

  • After switching the robot model and saving the project, the original robot model was not deleted.

  • Due to pose value precision differences, inverse kinematics solutions for special configuration robots were inaccurate.

  • When simulating path planning, the path planning tool showed that the robot could not reach the target point precisely.

  • The collision model of ring-shaped target objects generated by the software was inaccurate.

  • When a held target object collided with a point cloud column, the displayed point cloud collision position in the 3D simulation space was inaccurate.

  • In a workflow, if you hold down the left mouse button to connect Steps while pressing the Delete key on the keyboard to delete a Step, and then release the mouse button after connection is complete, the software would crash.

  • The number of rows setting for the windmill stack in the "Predefined Pallet Pattern" Step was not taking effect.

  • Some abnormal issues with Palletizing Steps.

  • Other software crash issues.

  • Workflow runtime exceptions.


Is this page helpful?

You can give a feedback in any of the following ways:

We Value Your Privacy

We use cookies to provide you with the best possible experience on our website. By continuing to use the site, you acknowledge that you agree to the use of cookies. If you decline, a single cookie will be used to ensure you're not tracked or remembered when you visit this website.