How to Troubleshoot Failed Master-Control Communications?

You are currently viewing the documentation for the latest version (2.1.2). 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 the Master-Control communication cannot be established between the Mech-Mind Vision System and the robot, the following reasons may be responsible. You can check the configuration items based on the sequence of this guide.

1. Controller System

1.1. Check if the Required Control Modules are Installed

Problem

Some control modules required for the robot brand are not installed.

Solution

Make sure that the control modules are installed on the robot system based on the communication setup instructions of the robot brand.

1.2. Robot or Controller Version Is Incompatible with the Vision System Version

Problem

Robot producers upgrade robot controllers constantly. Your controller version and the controller version supported by the Mech-Mind Vision System may not be the same. In such cases, if you load Master-Control programs to your robot, issues such as data inconsistencies across ports, mismatched robot command functionalities, and program code incompatibilities may occur. Therefore, you need to check if you want to proceed with the Master-Control communication.

Solution

  • If your controller model and the supported controller model are inconsistent, your controller model is very likely not supported by the Mech-Mind Vision System for Master-Control communication.

  • If the controller model matches the supported controller model but the version numbers differ, the on-site engineer can attempt to proceed with the Master-Control communication according to the provided documentation. However, in such cases, Mech-Mind does not guarantee that the Master-Control communication you set up can work normally. If you have any questions, please contact Mech-Mind technical support.

2. Networks

2.1. Specified Robot IP Port and the Used Port Are Inconsistent

Problem

Some robot brands may provide two Ethernet ports such as port 1 and port 2 on their CPU motherboard. The Ethernet cable is plugged into port 1, but an IP address that matches port 2 is specified.

Solution

Open the controller and ensure that the port into which the Ethernet cable is plugged matches the specified IP address.

2.2. Specified IPC IP Port and the Used Port Are Inconsistent

Problem

Some IPC brands may provide two Ethernet ports such as port 1 and port 2 on their CPU motherboard. The Ethernet cable is plugged into port 1, but an IP address that matches port 2 is specified.

Solution

Repeatedly plug and unplug the IPC’s Ethernet cable while observing the network adapter panel to monitor the connection status. This way, the correspondence between ports and IP addresses can be determined.

2.3. Improper Firewall Settings of IPC

Problem

The firewall of the IPC determines that the connection between the vision system and the robot is malicious and then closes the connection.

Solution

Disable all firewall settings or configure proper firewall rules. For more information, see How to Troubleshooting Failed Communications Caused by Firewalls?.

2.4. Improper Router Settings

Problem

When the settings of the router are improper, the communication cannot be established.

Solution

Disable the router and then test the direct communication between the vision system and the robot. If the direct communication between the vision system and the robot can be established, test the communication of the two sides using a router. If the communication of the two sides using a router fails, see the router manual to check the router settings.

2.5. IPC and Robot IP Addresses Are Not in Same Subnet

Problem

The IP address or subnet mask settings of the IPC or the robot are improper, causing them to be on different subnets and preventing communication.

Solution

Check the IP address and subnet mask settings of the IPC and the robot to make sure that the two IP addresses reside in the same subnet, and then test whether the communication can be established by using the two IP addresses. If the communication can be established, the two IP addresses are valid.

2.6. Robot IP Address in Mech-Viz and Real Robot IP address Are Inconsistent

Problem

The robot IP address specified in the following interface and the real robot IP address are inconsistent, casing failed communications.

faq1

Solution

Make sure that the specified robot IP address is the real robot IP address.

3. Master-Control Programs

If you do not need to load Master-Control programs, please skip this section.

3.1. Other Foreground or Background Programs Are Running When the Program Files Are Being Loaded

Problem

When a Master-Control program file is being loaded to a robot that contains the same program, the loading will fail because the same program is being used.

Solution

On the teach pendant interface, disable the foreground or background program for the robot.

3.2. Incorrect Master-Control Program Files Are Loaded

Problem

When the incorrect Master-Control program file is loaded, the communication will fail.

Solution

On the teach pendant interface, make sure that the correct Master-Control program file is loaded to the robot system.

3.3. Master-Control Programs Are Not Running

Problem

When the Master-Control program is not running or is stopped, the communication will fail.

Solution

On the teach pendant interface, make sure that the Master-Control program is running.

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.