Status Codes and Trouble Shooting¶

Overview¶

Range	Category
1001—1099	Mech-Vision error codes
1100—1199	Mech-Vision normal status codes
2001—2099	Mech-Viz error codes
2100—2199	Mech-Viz normal status codes
3001—3099	Mech-Center error codes
3100—3199	Mech-Center normal status codes
4000—4099	Robot error codes
4100—4199	Robot normal status codes
7001—7099	Hand-eye calibration error codes
7100—7199	Hand-eye calibration normal status codes

Mech-Vision¶

Mech-Vision Error Codes¶

Code	Meaning
1001	Mech-Vision: Project not registered.
1002	Mech-Vision: No vision result.
1003	Mech-Vision: No point cloud in ROI.
1004	Mech-Vision: Parameter setting failed.
1005	Mech-Vision: Invalid pose type.
1006	Mech-Vision: Invalid pose data.
1008	Error code not in use.
1009	Mech-Vision: Number of poses and number of motion parameters do not match.
1010	Mech-Vision: Number of poses and number of labels do not match.
1011	Mech-Vision: Project number does not exist.
1012	Mech-Vision: Parameter recipe number out of range.
1013	Mech-Vision: Parameter recipe does not exist.
1014	Mech-Vision: Failed to set parameter recipe.
1015	Mech-Vision: Project runtime error.
1016	Mech-Vision: Failed to start deep learning server.
1017	Mech-Vision: Invalid label mapping.
1018	Mech-Vision: Wrong number of vision points.
1019	Mech-Vision: Execution timed out.
1020	Mech-Vision: Not executed.
1021	Mech-Vision: Failed to set box dimensions; please confirm if Step Read Object Dimensions is in the project.
1022	Mech-Vision: Invalid setting values of object dimensions.
1024	Mech-Vision: Number of poses and number of custom data items do not match.
1025	Mech-Vision: Using virtual camera. Image data has been blocked.

Mech-Vision Normal Status Codes¶

Code	Meaning
1100	Mech-Vision: Successfully obtained vision points.
1101	Mech-Vision: Ready.
1102	Mech-Vision: Successfully triggered project.
1107	Mech-Vision: Successfully switched parameter recipe.
1108	Mech-Vision: Successfully set object dimensions.

Mech-Viz¶

Mech-Viz Error Codes¶

Code	Meaning
2001	Mech-Viz: Project not registered.
2002	Mech-Viz: Project is running.
2003	Mech-Viz: Vision result from Mech-Vision not received.
2004	Mech-Viz: Failed to reach vision point from Mech-Vision.
2005	Mech-Viz: Failed to calculate robot JPs.
2006	Error code not in use.
2007	Mech-Viz: Path planning failed.
2008	Mech-Viz: Project runtime error.
2009	Mech-Viz: TCP not provided.
2010	Mech-Viz: Path not reachable.
2011	Mech-Viz: DO list not provided.
2012	Mech-Viz: Invalid pose type.
2013	Mech-Viz: Invalid pose data.
2014	Mech-Viz: Project not set.
2015	Mech-Viz: Pose of TCP type not supported.
2016	Mech-Viz: Parameter setting failed.
2017	Mech-Viz: Failed to stop execution.
2018	Mech-Viz: Invalid branch_by_msg Task exit number.
2019	Mech-Viz: Failed to set branch_by_msg Task; please confirm whether the Task ID exists.
2020	Mech-Viz: Motion error—singularity.
2021	Mech-Viz: MoveL planning failed.
2022	Mech-Viz: Not executed.
2023	Mech-Viz: Project file error.
2024	Mech-Viz: Invalid branch_by_msg Task ID.
2025	Mech-Viz: Execution timed out.
2026	Mech-Viz: Invalid ID of Task with index parameter.
2027	Mech-Viz: Invalid index value.
2028	Mech-Viz: Index setting failed; please check whether the Task with index parameter exists in the project.
2029	Mech-Viz: Failed to set target of outer_move Task.
2030	Mech-Viz: Invalid vision point.
2031	Mech-Viz: Robot self-collision detected.
2032	Mech-Viz: Collision between robot and scene object detected.
2033	Mech-Viz: Collision detected as point cloud collision point count exceeds threshold.
2034	Mech-Viz: Collision detected as point cloud collision area exceeds threshold.
2035	Mech-Viz: Collision detected as point cloud collision volume exceeds threshold.
2036	Mech-Viz: Vision service did not capture image.
2037	Mech-Viz: No vision result from vision service.
2038	Mech-Viz: No point cloud in ROI in vision result.
2039	Mech-Viz: No vision point for planning.
2040	Mech-Viz: Failed to plan paths for some of vision points from vision result reuse.
2041	Mech-Viz: Failed to get Task parameter.
2042	Mech-Viz: Failed to obtain planning result of outer_move.
2043	Mech-Viz: Failed to get custom data in vision result.
2044	Mech-Viz: Vision service not registered.

Mech-Viz Normal Status Codes¶

Code	Meaning
2100	Mech-Viz: Successfully executed.
2101	Mech-Viz: Successfully stopped execution.
2102	Mech-Viz: Successfully sent DO list.
2103	Mech-Viz: Successfully started.
2104	Mech-Viz: Successfully stopped.
2105	Mech-Viz: Branch successfully set.
2106	Mech-Viz: Index successfully set.
2107	Mech-Viz: Target of outer_move Task successfully set.

Mech-Center¶

Mech-Center Error Codes¶

Code	Meaning
3001	Mech-Center: Illegal command.
3002	Mech-Center: Interface command length or format error.
3003	Mech-Center: Client disconnected.
3004	Mech-Center: Server disconnected.
3005	Mech-Center: Calling Mech-Vision timed out.
3006	Mech-Center: Unknown error.
3007	Mech-Center: Data acknowledge signal timed out.
3008	Mech-Center: Config ID does not exist; failed to read/set Task parameter.

Mech-Center Normal Status Codes¶

Code	Meaning
3100	Mech-Center: Client connection normal.
3101	Mech-Center: Server connection normal.
3102	Mech-Center: Waiting for client to connect.
3103	Mech-Center: Data cache cleared successfully.

Robot¶

Robot Error Codes¶

Code	Meaning
4001	Robot: Invalid robot type.
4002	Robot: Robot Euler angle type not supported.
4003	Robot: Robot service not registered.
4004	Robot: Missing robot parameters.
4005	Robot: Failed to connect to robot. Please check the robot IP address and network configuration.
4006	Robot: The robot burn-in program version is not up to date. Please download the new program.

Robot Normal Status Codes¶

Code	Meaning
4100	Robot: Robot service registered successfully.
4101	Robot: Successfully connected to the robot.
4102	Robot: Robot disconnected.
4103	Robot: User closed robot service.

Hand-Eye Calibration¶

Hand-Eye Calibration Error Codes¶

Code	Meaning
7001	Calibration: Parameter error.
7002	Calibration: Mech-Vision did not output calibration point.
7003	Calibration: Robot failed to reach calibration point.

Hand-Eye Calibration Normal Status Codes¶

Code	Meaning
7100	Calibration: Robot successfully reached calibration point.
7101	Calibration: Mech-Vision normally output calibration point.

Mech-Vision Trouble Shooting¶

1001¶

Mech-Vision: Project not registered.

Reason:

The project is not open in Mech-Vision.

Autoload Project has not been set for the Mech-Vision project.

Solution:

Make sure the project is open in Mech-Vision.

Make sure Autoload Project has been set for the Mech-Vision project.

1002¶

Mech-Vision: No vision result.

Reason:

The Mech-Vision project called has been successfully executed but has empty output. Possible reasons for empty output include exceedingly high confidence threshold for instance segmentation, no matched object in the scene, improper ROI settings, low point cloud quality, improper filtering settings, etc.

Command 102 has been called to obtain all poses in the vision result, and the cache is empty, but the user continues to call command 102.

Solution:

Check the data flow of the Mech-Vision project by going up from the PoseList port of Step “Procedure Out”.

Check the client interface program. If the parameter “pose transmission completion status” in the returned data of command 102 is 1, all poses have been transmitted, and continuing calling command 102 will result in this error.

Returned data format of command 102: 102, status code, pose transmission completion status, number of poses, reserved field, [pose, label, velocity].

1003¶

Mech-Vision: No point cloud in ROI.

Reason:

The Mech-Vision project called has been successfully executed, but there is no point cloud in the 3D ROI.

Solution:

Please check the ROI settings in the Step that sets the 3D ROI on the point cloud. For some projects, this error code can be used to determine whether the bin has been emptied or whether the bin has not been moved to a proper position. So, this error is not necessarily a project execution error.

1004¶

Mech-Vision: Parameter setting failed.

1005¶

Mech-Vision: Invalid pose type.

Reason:

The parameter that sets the pose type in command 101 has an illegal value.

Format of command 101: 101, project number, expected number of vision points, pose type, robot pose

Values of the parameter “pose type”:

0: no image-capturing robot pose is needed (such as in the eye-to-hand mode).

1: the image-capturing robot pose is in JPs.

2: the image-capturing robot pose is a flange pose.

Solution:

Check the client interface program. The value of the parameter “pose type” should be in the range of [0, 2].

1006¶

Mech-Vision: Invalid pose data.

Reason:

The pose data sent by command 101 does not consist of 6 numbers. The robot pose is a 6-axis robot pose by default. If the robot is a 4-axis or a 5-axis robot, please fill the remaining fields with 0.

Format of command 101: 101, project number, expected number of vision points, pose type, robot pose

Solution:

Check the client interface program. The robot pose data sent by command 101 should consist of 6 numbers.

1008¶

Error code not in use.

1009¶

Mech-Vision: Number of poses and number of motion parameters do not match.

Reason:

This error usually occurs in projects in which the vision result forms a robot motion path (such as gluing applications).

Solution:

Not available yet.

1010¶

Mech-Vision: Number of poses and number of labels do not match.

Reason:

The number of poses and number of labels output from the preceding Steps of Step “Procedure Out” do not match.

Solution:

Check the poses and labels in the data flow of the Mech-Vision project.

1011¶

Mech-Vision: Project number does not exist.

Reason:

The project number set in the parameter of command 101 does not exist in the deployment settings of Mech-Center.

For example, when there is only one project’s path in the deployment settings, if command 101 calls for project No. 2, the error will be raised.

Solution:

Check if the corresponding Mech-Vision projects all have Autoload Project checked.

Check the client interface program and make sure command 101 has the correct project number in its parameter.

1012¶

Mech-Vision: Parameter recipe number out of range.

Reason:

The parameter recipe number in command 103 does not have the corresponding recipe set in the Mech-Vision project.

For example, when there are only two parameter recipes in the Mech-Vision project, if command 103 is to set parameter recipe No. 3, this error will be raised.

Solution:

Check if the Mech-Vision project has the parameter recipe to be set.

Check if the client interface program correctly calls command 103.

1013¶

Mech-Vision: Parameter recipe not set.

Reason:

The client interface program calls command 103 to set the parameter recipe, but there is no parameter recipe set in the Mech-Vision project.

Solution:

Check the parameter recipe settings in the Mech-Vision project, and ensure the parameter recipes and their numbers are correct.

If the project does not require switching parameter recipes, please do not call command 103.

1014¶

Mech-Vision: Failed to set parameter recipe.

Reason:

The connection between Mech-Center and Mech-Vision is not established.

Solution:

Please restart Mech-Center and Mech-Vision.

1015¶

Mech-Vision: Project runtime error.

Reason:

The Mech-Vision project has runtime error with error code CV-Exxxx or has other errors for which Mech-Center does not have analyses. When such an error occurs, the Mech-Vision project is terminated without finishing execution.

Solution:

Check the error message in Mech-Vision and modify the Mech-Vision project if necessary.

1016¶

Mech-Vision: Failed to start deep learning server.

Reason:

The called Mech-Vision project has a deep learning Step(s), but the deep learning server has not been started. The corresponding error message in Mech-Vision is DL-E0201 deep learning server not started.

Solution:

Check if the Mech-Vision project is executed for the first time. Check if the time cost for starting the deep learning server is too long. If model pre-loading is required, please check “Preload Mode When Opening Project” in the parameters of the deep learning Step.

Check if the deep learning environment has been installed properly.

1017¶

Mech-Vision: Invalid label mapping.

Reason:

The label(s) in the vision result from Mech-Vision is not INT data. When using the standard interface, string labels should be mapped to integer labels using Step “Label Mapping”, otherwise this error will occur.

Solution:

Check the data flow in Mech-Vision, if the labels input to Step “Procedure Out” are not integers, please map the labels to positive integers using Step “Label Mapping”.

1018¶

Mech-Vision: Wrong number of vision points.

Reason:

The client interface program calls command 101 to trigger the Mech-Vision project. In the command’s parameter, the number of vision points to expect Mech-Vision to output exceeds the data length of the interface.

Format of command 101: 101, project number, expected number of vision points, pose type, robot pose

The data length can be set in the deployment settings of Mech-Center. Please set the max number of poses sent each time under Mech-Interface -> Advanced Settings. Range: [1, 30].

Solution:

Check the client interface program and make sure the parameter “number of poses” is smaller than the setting in Mech-Center.

1019¶

Mech-Vision: Execution timed out.

Reason:

After calling command 102 to obtain the vision result and the timing has started, the Mech-Vision project did not finish execution within the specified time.

The timeout period can be set under Mech-Interface -> Advanced Settings in the deployment settings of Mech-Center. The default timeout period is 10 seconds.

Solution:

Check the client interface program. A delay operation can be added before calling command 102.

For a Mech-Vision project that takes a long time to execute, the timeout period can be set longer in the deployment settings.

1020¶

Mech-Vision: Not executed.

Reason:

The client interface program did not call command 101 to start the Mech-Vision project but went on to call command 103 to try to get the vision result.

For example, if two Mech-Vision projects are registered in Mech-Center, if the client interface program starts project 1, but then tries to get the vision result of project 2, this error will occur.

Solution:

Check the client interface program and make sure the project number specified by command 102 is correct.

1021¶

Mech-Vision: Failed to set object dimensions; please confirm if Step Read Object Dimensions is in the project.

Reason:

The client interface program calls command 501 to try to input object dimensions to the Mech-Vision project, but the Mech-Vision project does not have a “Read Object Dimensions” Step.

Solution:

Check the Mech-Vision project and make sure it has a “Read Object Dimensions” Step.

1022¶

Mech-Vision: Invalid setting values of object dimensions.

Reason:

The client interface program calls command 501 to try to input object dimensions to the Mech-Vision project, but the dimension values are invalid (zero or negative values).

Solution:

Check the client interface program and make sure command 501 passes valid dimension values (positive real numbers).

1024¶

Mech-Vision: Number of poses and number of custom data items do not match.

Reason:

After the client interface program calls command 110, in the returned data, the number of poses and number of items of a custom data type do not match. A custom data type refers to data input to a port other than PoseList and LabelList of Step “Procedure Out” in the Mech-Vision project. Possible cases include:

Empty data at the custom data port.

List length at the custom data port does not equal the pose list length.

Suppose the number of poses input to Step “Procedure Out” is N. It is required that any custom data port (data other than poses and labels) either has 1 item or N item. Otherwise, this error will be raised.

For example, if the custom port data is the number of objects obtained by instance segmentation, only 1 data item is required, and each time the command is executed, the same value will be returned; if the custom data is the box dimensions, N data items are required, and each time the command is executed, the “box dimensions” data corresponding to the pose will be returned.

Solution:

Please check the data flow in the Mech-Vision project.

1025¶

Mech-Vision: Using virtual camera. Image data has been blocked.

Mech-Viz Trouble Shooting¶

2001¶

Mech-Viz: Project not registered.

Reason:

The project is not open in Mech-Viz.

The project specified by the command 201 called does not have Autoload enabled.

Solution:

Make sure the project is open in Mech-Viz.

Make sure Autoload has been enabled for the Mech-Viz project.

2002¶

Mech-Viz: Project is running.

Reason:

When a Mech-Viz project is still running, command 201 is called to trigger the Mech-Viz project.

Solution:

Make sure the client interface program does not call twice command 201 to trigger the same Mech-Viz project within a short time.

2003¶

Mech-Viz: Vision result from Mech-Vision not received.

Reason:

Task “check_look” does not find any vision result and takes the 2nd exit (“no result”), and the project ends.

Solution:

If necessary, add additional Tasks to the “no result” exit of Task “check_look”.

Check if the workobjects have all been picked away.

Check the Mech-Vision project to see if settings such as ROI settings, instance segmentation confidence threshold, etc. are proper.

2004¶

Mech-Viz: Failed to reach vision point from Mech-Vision.

Reason:

The pose in the vision point from vision service is out of the reachable range of the robot.

Solution:

Check if the point cloud position in Mech-Viz is normal.

Check if the camera extrinsic parameters are normal.

Check if the robot TCP settings in Mech-Viz are normal and whether any workobject is out of the reachable range of the robot.

2005¶

Mech-Viz: Failed to calculate robot JPs.

Reason:

Mech-Viz failed to calculate robot JPs for a target.

Solution:

Not available yet.

2006¶

Error code not in use

2007¶

Mech-Viz: Path planning failed.

Reason:

Mech-Viz failed to plan a path for any of the vision points in the vision result, and not all reasons for plan failures of the vision points are the same.

(If the planning failed on the vision points for the same reason, the corresponding error code for such a reason will be raised)

For example, if there are 40 vision points in the vision result, for 20 of which the planning failed because the robot cannot reach the vision point, and for 20 of which the planning failed because collisions were detected, this error will be raised.

Solution:

Check the plan history in Mech-Viz.

2008¶

Mech-Viz: Project runtime error.

Reason:

An error occurred when the Mech-Viz project was running and the project has been terminated. The error may be reported by a Mech-Viz error code MP-Exxxx or may not yet have an analysis.

Solution:

Check the pop-up window or logs of Mech-Viz.

2009¶

Mech-Viz: TCP not provided.

Reason:

The client interface program calls command 205 to obtain the planned path from the robot, and requires that the targets should be robot TCPs, but the returned data does not contain robot TCPs.

Solution:

In Mech-Viz, check the “Others” panel and make sure the option “Send TCP” is checked.

2010¶

Mech-Viz: Path not reachable.

Reason:

An error with Mech-Viz error code MP-E0007 occurred when running the Mech-Viz project.

Solution:

Not available yet.

2011¶

Mech-Viz: DO list not provided.

Reason:

The client program calls command 206 to obtain the DO signal list that controls the tool (sectioned suction cups, array gripper, etc.), but in the Mech-Viz project, no DO signal list has been configured.

Solution:

Check whether there is a set_do_list Task that follows the visual_move Task. In the parameters of the set_do_list Task, under “Receiver”, “StandardInterface” should be checked.

2012¶

Mech-Viz: Invalid pose type.

Reason:

The client interface program calls command 201 to trigger the Mech-Viz project, the value of the parameter “pose type” is illegal.

Format of command 201: 201, pose type, robot pose.

Values of parameter “pose type”:

0: no image-capturing pose is required (such as in the eye-to-hand mode).

1: the robot pose is in JPs.

The client interface program calls command 205 to obtain the planned path, the value of the parameter “expected pose type” is illegal.

Format of command 205: 205, expected pose type.

Values of parameter “expected pose type”:

1: the returned pose type is expected to be JPs.

2: the returned pose type is expected to be TCP.

Solution:

Check the command sent by the client interface program.

2013¶

Mech-Viz: Invalid pose data.

Reason:

The client interface program calls command 201 to trigger the Mech-Viz project, the robot pose data sent is not in the format of 6 numbers. The robot pose is a 6-axis robot pose by default. If the robot is a 4-axis or a 5-axis robot, please fill the remaining fields with 0.

Format of command 201: 201, pose type, robot pose.

Solution:

Check the robot pose data in command 201 sent by the client interface program. If the Mech-Viz project does not require inputting robot pose data, please set the parameter “pose type” to 0.

2014¶

Mech-Viz: Project not set.

Reason:

The project is not open in Mech-Viz.

The Mech-Viz project does not have Autoload checked.

Solution:

Make sure the project is open in Mech-Viz and has Autoload checked.

2015¶

Mech-Viz: Pose of TCP type not supported.

Reason:

The client interface program calls command 201 to trigger the Mech-Viz project, the pose type set is TCP, but currently Mech-Viz does not support inputting robot pose as TCP.

Solution:

Make sure the parameter “pose type” in command 201 sent by the client interface program is set to either 0 or 1.

Format of command 201: 201, pose type, robot pose.

Values of parameter “pose type”:

0: no image-capturing pose is required (such as in the eye-to-hand mode).

1: the robot pose is in JPs.

2016¶

Mech-Viz: Parameter setting failed.

Reason:

An error occurred when the client interface program called command 208 to set a parameter of a Task in the Mech-Viz project.

Solution:

Check if the Task ID and parameter key name in the configuration file are correct.

The configuration file (Property Config) can be found under Deployment Settings -> Mech-Interface -> Advanced Settings in Mech-Center.

2017¶

Mech-Viz: Failed to stop execution.

Reason:

The client interface program calls command 202 to stop the running of the Mech-Viz project, but the project does not stop within 5 seconds.

Solution:

Not available yet.

2018¶

Mech-Viz: Invalid branch_by_msg Task exit number.

Reason:

The client interface program calls command 203 to set the exit of the branching Task in the Mech-Viz project. In the command, the exit number is less than or equal to 0 or is greater than the total number of exits of the Task.

Format of command 203: 203, branching Task ID, exit number

Solution:

Check the exits of the branching Task in the Mech-Viz project.

Check the exit number set in command 203.

2019¶

Mech-Viz: Failed to set branch_by_msg Task; please confirm whether the Task ID exists.

Reason:

The client interface program calls command 203 to set a branch in Mech-Viz, but the branching Task ID set in the command either does not exist in the Mech-Viz project or is not a positive integer.

The ID of a Task in Mech-Viz can be found and set in the Task’s parameters.

Format of command 203: 203, branching Task ID, exit number

Solution:

Make sure the Task ID sent by the command has a corresponding Task in Mech-Viz.

Make sure the Task IDs set in the command and in the Mech-Viz projects are positive integers.

2020¶

Mech-Viz: Motion error—singularity.

Reason:

When Mech-Viz is planning the robot path, a robot singularity is encountered.

Solution:

Check where the singularity is in the Mech-Viz project and modify the corresponding targets.

2021¶

Mech-Viz: MoveL planning failed.

Reason:

Mech-Viz found that the robot cannot reach a target by linear motion.

Solution:

Modify the target or add intermediate points.

Change the motion type to joint motion.

2022¶

Mech-Viz: Not executed.

Reason:

The client interface program calls command 203 to set branch, but the Mech-Viz project is not running.

The client interface program calls command 205 to get the planned path but the Mech-Viz project has not been executed.

The client interface program calls command 205 to get the planned path but the Mech-Viz project does not have an output.

Solution:

Check the client interface program to make sure that the Mech-Viz project is running when setting the branch.

Check the client interface program to make sure that the Mech-Viz project is executed before getting the planned path.

2023¶

Mech-Viz: Project file error.

2024¶

Mech-Viz: Invalid branch_by_msg Task ID.

Reason:

The client interface program calls command 203 and sets a Task ID that is not a positive integer.

Format of command 203: 203, branching Task ID, exit number

Solution:

Make sure the parameter “branching Task ID” of command 203 is a positive integer.

The ID of a Task in Mech-Viz can be found and set in the Task’s parameters.

2025¶

Mech-Viz: Execution timed out.

Reason:

The client interface program calls command 205 to get the planned path from Mech-Viz, but the project execution does not finish within the specified time (10 seconds by default).

Solution:

Check the normal project execution time cost of the Mech-Viz project. If the time cost is longer than 10 seconds, please adjust the settings under Mech-Interface -> Advanced Settings in the deployment settings of Mech-Center.

In the client interface program, a delay can be inserted in the client interface program before calling command 205.

2026¶

Mech-Viz: Invalid ID of Task with index parameter.

Reason:

The client interface program calls command 204 to set the index parameter of a Task with index parameter, and the Task ID is not a positive integer.

Format of command 204: 204, Task ID, index value

Solution:

Check the client interface program and make sure that the Task ID set in command 204 is a positive integer.

The ID of a Task in Mech-Viz can be found and set in the Task’s parameters.

2027¶

Mech-Viz: Invalid index value.

Reason:

The client interface program calls command 204 to set the index parameter of a Task with an index parameter, and the index value is not a positive integer.

Format of command 204: 204, Task ID, index value

Solution:

Check the client interface program and make sure that the index value set in command 204 is a positive integer.

2028¶

Mech-Viz: Index setting failed; please check whether the Task with index parameter exists in the project.

Reason:

The client interface program calls command 204 to set the index parameter of a Task with index parameter, and the Task ID does not have a corresponding Task in the Mech-Viz project.

Format of command 204: 204, Task ID, index value

Solution:

Check the client interface program and make sure the Task ID set in command 204 has a corresponding Task in the Mech-Viz project. A Task’s ID can be found and set in its parameters in Mech-Viz.

2029¶

Mech-Viz: Failed to set target of outer_move Task.

2030¶

Mech-Viz: Invalid vision point.

Reason:

Unknown error. Mech-Viz error code: MP-E0010

Solution:

Not available yet.

2031¶

Mech-Viz: Robot self-collision detected.

Reason:

Mech-Viz detected robot self-collision and the path planning failed.

Solution:

Check the corresponding target in the Mech-Viz project.

2032¶

Mech-Viz: Collision between robot and scene object detected.

Reason:

Mech-Viz detected collision between the robot and scene object model(s) and the path planning failed.

Solution:

Check the corresponding target and scene object(s) in the Mech-Viz project.

2033¶

Mech-Viz: Collision detected as point cloud collision point count exceeds threshold.

Reason:

Mech-Viz detected collision between the robot and workobject. The number of point cloud points involved in the collision is above the threshold. The path planning failed.

Solution:

Check the corresponding target in the Mech-Viz project.

Check the setting of the collision point count threshold and modify it if necessary.

2034¶

Mech-Viz: Collision detected as point cloud collision area exceeds threshold.

Reason:

Mech-Viz detected collision between the robot and workobject. The surface area involved in the collision is above the threshold. The path planning failed.

Solution:

Check the corresponding target in the Mech-Viz project.

Check the setting of the collision area threshold and modify it if necessary.

2035¶

Mech-Viz: Collision detected as point cloud collision volume exceeds threshold.

Reason:

Mech-Viz detected collision between the robot and workobject. The volume involved in the collision is above the threshold. The path planning failed.

Solution:

Check the corresponding target in the Mech-Viz project.

Check the setting of the collision volume threshold and modify it if necessary.

2036¶

Mech-Viz: Vision service did not capture image.

Reason:

In the Mech-Viz project, the “check_look” Task takes the 4th exit (“(vision service) not called”), and the exit is not connected to any further Tasks. The Mech-Viz project terminates.

Solution:

Check whether the vision services selected in “visual_look” and “check_look” are consistent.

2037¶

Mech-Viz: No vision result from vision service.

Reason:

In the Mech-Viz project, the “check_look” Task takes the 2nd exit (“no result”), and the exit is not connected to any further Tasks. The Mech-Viz project terminates. The corresponding Mech-Vision project does not have a vision result output.

Solution:

Please see the solution of 1002.

2038¶

Mech-Viz: No point cloud in ROI in vision result.

Reason:

In the Mech-Viz project, the “check_look” Task takes the 5th exit (“no point cloud in ROI”), and the exit is not connected to any further Tasks. The Mech-Viz project terminates. The corresponding Mech-Vision project does not have a vision result output.

Solution:

Please see the solution of 1002.

2039¶

Mech-Viz: No vision point for planning.

Reason:

In the Mech-Viz project, the Task visual_move does not have any vision point for planning. If in the project there is no “check_look” Task or the “check_look” Task takes the 2nd exit (“no result”) and the exit is not connected to any further Tasks, this error will occur.

Solution:

Please see the solution of 1002.

Check if the “check_look” Task is used correctly in the Mech-Viz project.

2040¶

Mech-Viz: Failed to plan paths for some of vision points from vision result reuse.

Reason:

In the Mech-Viz project, reusing the vision result is enabled (in the parameters of Task “visual_look”). The same vision result is used for multiple plannings, and some plannings failed.

When this error occurs, the successful planning will still be output.

Solution:

Check the plan history of Mech-Viz and locate why some planning failed.

2041¶

Mech-Viz: Failed to get Task parameter.

Reason:

The client interface program calls command 207 to read the parameter value of a Task in Mech-Viz but encounters an error.

Solution:

Check if the content of the configuration file is correct. The configuration file (Property Config) can be found under Deployment Settings -> Mech-Interface -> Advanced Settings in Mech-Center.

In particular, check if the Task ID and parameter key name are correct.

2042¶

Mech-Viz: Failed to get planning result of visual_move.

Reason:

The client interface program calls command 210 to get the planning result of visual_move from Mech-Viz but encounters an error.

Solution:

Not available yet.

2043¶

Mech-Viz: Failed to get custom data in vision result.

Reason:

The client interface program calls command 210 to get the planning result of visual_move and custom data in the vision result from Mech-Viz but encounters an error in getting the custom data part.

Solution:

Please see the solution of 1024.

2044¶

Mech-Viz: Vision service not registered.

Reason:

In the Mech-Viz project, the “visual_look” Task does not have a vision service selected.

Solution:

Please select a correct vision service in the “visual_look” Task.

Mech-Center Trouble Shooting¶

3001¶

Mech-Center: Illegal command.

Reason:

The format of the command sent by the client interface program is not supported.

Solution:

Please check the client interface program.

3002¶

Mech-Center: Interface command length or format error.

Reason:

The length of the command sent by the client interface program is illegal. For example, the robot pose data sent in the command does not consist of six numbers.

The format of the command sent by the client interface program is illegal. For example, commas are used as separators.

Solution:

Please check the client interface program.

3003¶

Mech-Center: Client disconnected.

3004¶

Mech-Center: Server disconnected.

3005¶

Mech-Center: Calling Mech-Vision timed out.

3006¶

Mech-Center: Unknown error.

3007¶

Mech-Center: Data acknowledge signal timed out.

Reason:

When using PROFINET/EthernetIP:

When sending the pose data to the port, Mech-Center needs to check that the signal “data_acknowledge” is 0. If in the specified time, the client interface program does not reset the signal “data_acknowledge” to 0, this error will be raised.

After sending the pose data to the port, Mech-Center needs to check that the signal “data_acknowledge” is 1, indicating that the data has been read. If in the specified time, the client interface program does not set the signal “data_acknowledge” to 1, this error will be raised.

Solution:

Check the client interface program and make sure that the signal “data_acknowledge” is 0 before calling command 102 or command 205.

Check the client interface program and make sure that the signal “data_acknowledge” is set to 1 immediately after reading the data from Mech-Center.

3008¶

Mech-Center: Config ID does not exist; failed to read/set Task parameter.

Reason:

The client interface program calls command 207 to read a Task parameter value or command 208 to set a Task parameter value, but the corresponding content is not found in the configuration file.

The configuration file (Property Config) can be found under Deployment Settings -> Mech-Interface -> Advanced Settings in Mech-Center.

Solution:

Check the configuration file and make sure the config ID is a positive integer, and the content is correct.

Hand-Eye Calibration Trouble Shooting¶

7001¶

Calibration: Parameter error.

Reason:

The client interface program sends the robot pose while performing calibration, but the robot pose does not consist of six numbers. The robot pose is a 6-axis robot pose by default. If the robot is a 4-axis or a 5-axis robot, please fill the remaining fields with 0.

Solution:

Check the robot pose data sent by the client interface program

7002¶

Calibration: Mech-Vision did not output calibration point.

Reason:

During calibration, Mech-Vision does not send the robot pose to Mech-Center.

Solution:

Not available yet.

7003¶

Calibration: Robot failed to reach calibration point.