Communication Mode Selection

You are currently viewing the documentation for version 1.7.5. To access documentation for other versions, click the "Switch Version" button located in the upper-right corner of the page.

■ To use the latest version, visit the Mech-Mind Download Center to download it.

■ If you're unsure about the version of the product you are using, please contact Mech-Mind Technical Support for assistance.

In actual deployment, you usually need to collect the functional requirements, communication objects and communication protocols of the project first, and then determine the communication mode according to them.

The following figure shows the procedure of selecting the communication mode.

communication mode selection

When selecting the communication mode, determine whether to use Master-Control communication or interface communication first. If you need to use interface communication, further determine whether to use Standard Interface communication or Adapter communication.

The procedure of determining whether to use Master-Control communication or interface communication is as follows:

  1. Determine whether the communication object is a robot.

    • If yes, proceed to the next step;

    • If no, use interface communication.

  2. Determine whether the project requires that Mech-Viz should be used to control the robot.

    • If yes, proceed to the next step;

    • If no, use interface communication.

  3. Determine whether the Master-Control communication mode supports all the robot functions required by the project, such as robot returning the same way after collision.

    • If yes, use Master-Control communication;

    • If no, use interface communication.

The procedure of determining whether to use Standard Interface communication or Adapter communication is as follows:

  1. Determine whether Standard Interface communication supports the communication objects and communication protocols of the project.

    • If yes, proceed to the next step;

    • If no, use Adapter communication.

  2. Determine whether Standard Interface communication meets the functional requirements of the project.

    • If yes, use Standard Interface communication;

    • If no, use Adapter communication.

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.