Error Codes

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.

If an external device sends a command to Mech-MSR during communication and the command fails to execute, an error code is returned.

-1

Error: The project ID does not exist.

Possible causes:

  • The specified project ID does not exist in the Project List of Mech-MSR.

  • The specified project is newly created, and the solution containing the project has not been closed and reopened.

Solutions:

  • Make sure that the specified project ID exists in the Project List of Mech-MSR.

  • Try closing and reopening the solution that contains the project in Mech-MSR.

-2

Error: No result.

Possible cause: The specified project has not been triggered to run.

Solution: Make sure that the project has been triggered to run through the trigger command (command code 2) or the execute command (command code 1).

-3

Error: Project execution timed out.

Possible cause: The project runs for too long and exceeds the configured Execution timeout for return command.

Solutions:

Check whether the project execution time exceeds the timeout period and whether the long execution time is abnormal. If it is abnormal, locate and resolve the cause. If it is normal, increase the Execution timeout for return command appropriately in the Communication Configuration window.

-4

Error: Invalid command.

Possible cause: Mech-MSR cannot respond to an invalid command.

Solution: Check the sent command and make sure that it is correct.

-5

Error: Setting or retrieval failed.

Possible causes:

  • Switching the parameter recipe failed.

  • Switching the solution failed.

  • Reading the global variable failed.

  • Writing the global variable failed.

Solutions:

  • Make sure that the parameter recipe ID exists and that the parameter recipe is configured correctly.

  • Make sure that the solution ID exists and that the solution path is valid.

  • Make sure that the global variable ID exists, the data type matches, and communication is enabled for the variable in the Global Variable Manager.

  • Make sure that the global variable ID exists, the data type matches, and communication is enabled for the variable in the Global Variable Manager.

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.

  • Preference
  • I accept
  • I don't accept