Solution Deployment FAQs

You are currently viewing the documentation for the latest version (2.1.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.

This section introduces the common problems, possible causes, and solutions for the Square Steel Billets solution.

Problem 1: Long Path Planning Time

Symptom

The path planning by using Mech-Viz takes a long time, resulting in long robot wait time.

Possible Causes

  • The pose sequence output by Mech-Vision is unreasonable, leading to an increased number of path-planning failures in Mech-Viz.

  • There is a problem with the Mech-Viz project parameter configuration.

  • Multiple unnecessary attempts based on the rotational symmetry were made when using Mech-Viz for path planning.

Solution

  • Use the pose adjustment tool to filter poses, such as using the Filter by angle method to filter out poses with inappropriate picking angles.

problem 1 solution 1

  • Disable time-consuming and unnecessary features in Mech-Viz, such as turning off the switch next toProblem One under Solutions to common problems in the Collisions functional panel, i.e., do not remove the point cloud of the target object.

problem 1 solution 2

  • Make sure that all options under Improve Performance in the Mech-Viz toolbar are selected.

problem 1 solution 3

  • When configuring end tools, set the Order of symmetry value according to the actual situation, reducing unnecessary picking attempts.

problem 1 solution 4

Problem 2: Low Matching Accuracy in Z-Direction

Symptom

When edge matching is performed, the matching accuracy in the Z-direction is low.

problem 2 phenomenon

Possible Causes

The point clouds used for edge matching are of poor quality, reducing the accuracy in the Z-axis direction during edge matching.

Solution

Turn on the Advanced mode switch on the right of Recognize target object and Enable extra fine matching. This option will correct and refine the target object poses for matching, significantly improving the accuracy of pose data.

Question 3: Path Planning Failure

Symptom

The path planning failed when using Mech-Viz for path planning.

Possible Causes

  • The target object poses output by Mech-Vision are beyond the robot workspace.

  • The waypoint settings in Mech-Viz are unreasonable, resulting in collisions between the robot and scene objects.

  • When picking a target object with a tool, the tool collides with the point cloud representing the target object surface and the collision volume exceeds the Collision detection threshold.

Solution

  • Check if the target object poses output by Mech-Vision are correct.

  • Add appropriate intermediate waypoints in Mech-Viz according to the actual situation.

  • Consider whether collisions are allowed when the tool picks the target object.

    • If collisions are allowed, turn on the switch on the right of Problem 2 under Solutions to common problems in the Collisions functional panel and set the Non-detection range. Once this option is enabled, point cloud collisions in the adjacent area to the pick point will not be detected.

      problem 2 solution 3

    • If collisions are not allowed, check if the Collision detection threshold is too small. If this parameter value is appropriate, but the target object does collide with the tool, other picking strategies may be considered.

Problem 4: Point Cloud Model Matching Failure or Missed Recognition of Target Object

Symptom

During point cloud model matching, there are instances of matching failures or missed target objects.

problem 4 phenomenon

Possible Causes

  • The maximum number of poses obtained by matching has been reached.

  • The score of the matched pose is below the Confidence threshold.

  • Some target objects are overlapped by others and the Overlap ratio threshold is exceeded, leading to missed recognition.

  • Missing points in the target object point cloud results in missed recognition.

Solution

  • Adjusts the value of the Max outputs parameter.

  • Adjust the value of the Confidence threshold parameter according to the actual situation to remove the lower score poses.

  • In actual applications, a larger Coincidence ratio threshold and Overlap ratio threshold can be used if picking of the overlapped and coinciding target objects is allowed.

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.

  • Preference
  • I accept
  • I don't accept