Communication Component 1.7 Release Notes
This document introduces the new features, improvements, and resolved issues of Communication Component 1.7.
Communication Component 1.7.2 Release Notes
This document introduces the new features, improvements, and resolved issues of Communication Component 1.7.2.
New Features
Standard Interface Supports the Mitsubishi MELSEC Protocol
Standard Interface communication with the Mitsubishi PLC based on the Mitsubishi MELSEC protocol is supported. The vision system acts as the client, and the Mitsubishi PLC device acts as the server in the communication. You can configure the Standard Interface communication based on the Mitsubishi MELSEC protocol in “Robot and Interface Communication” of Mech-Vision.
Standard Interface Supports UDP
Standard Interface communication based on UDP is supported. The vision system acts as the server in the communication. The usage and commands are similar to that of the TCP/IP protocol. Among all supported robots, only HYUNDAI robots use UDP to communicate with the vision system.
Standard Interface Supports Integration with ROKAE Industrial Robots, HYUNDAI Industrial Robots, and NACHI Industrial Robots
Standard Interface has adapted to ROKAE industrial robots, HYUNDAI industrial robots, and NACHI industrial robots. Communication Component 1.7.2 has provided robot standard Interface programs for them.
New URCap Plugin 1.5.0 for PolyScope 6 System
URCap plugin 1.5.0 (1.5.0.urcap and 1.5.0.urcapx) is supported in Communication Component 1.7.2.
|
In UR PolyScope 6 system, the file extension of URCap plugin is .urcapx. PolyScope 6 is no longer compatible with the previous .urcap file. |
The compatible versions of PolyScope and Mech-Mind Software Suite for the URCap 1.5.0 plugins are shown in the table below. Please select the URCap plugin file according to the version of PolyScope used by the robot.
| URcap Plugin File | PolyScope Version | Mech-Mind Software Suite Version |
|---|---|---|
1.5.0.urcap |
e-Series: 5.9 or above (below 6.0)
|
1.7.2 |
1.6.2 |
e-Series: 6.0 or above |
1.7.2 |
1.7.0 |
e-Series: 5.3 or above (below 6.0)
|
1.6.1 or above |
Compared with URCap plugin 1.4.6, URCap plugin 1.5.0 has the following new features:
-
Can get the planned path from the “Path Planning” Step in Mech-Vision.
-
Support inputting the project ID, parameter recipe number, branch number, and exit port number by using variables.
-
Support receiving various output results from Mech-Vision, such as Basic (vision points and labels), Custom (vision points, labels, and data output by custom ports), and Planned path (waypoints and labels output by the “Path Planning” Step).
Standard Interface Supports Communication with AB PLC Based on EtherNet/IP
Standard Interface communication with the Allen‑Bradley PLC (hereafter referred to as AB PLC) based on EtherNet/IP is supported. The vision system acts as the slave device, and the AB PLC acts as the master device in the communication. You can configure the EtherNet/IP communication in “Robot and Interface Communication” of Mech-Vision.
Improvements
Notify the Robot That Command 101 Is Successfully Triggered after the Image Is Captured
In Eye In Hand scenarios using the software of previous versions, a “Notify” Step should be added after the “Capture Images from Camera” Step in the Mech-Vision project. This connection aimed to move the robot right after the image was captured, without waiting for the Mech-Vision project to stop.
In the new version, adding the “Notify” Step is no longer necessary. Instead, you can navigate to “Robot and Interface Configuration” > “Advanced Settings” in Mech-Vision and select Return “1102: Successfully triggered” after the capture. Once this option is selected, the robot will start to move after it triggers the Mech-Vision project and receives “1102: Successfully triggered”, thus reducing the cycle time.
|
In the new version, if Standard Interface based on PROFINET protocol is used, the robot can move after the image is captured in either of the following settings:
|
Resolved Issues
Communication Component 1.7.2 has fixed the following issues:
-
For automatic calibration with Standard Interface, a timeout might occur when setting calibration parameters in Mech-Vision.
-
An error might occur if the Mech-Viz branch was set immediately after the Mech-Viz project was triggered to run.
Communication Component 1.7.1 Release Notes
This topic introduces the resolved issues in Communication Component 1.7.1.
Resolved Issues
The following issues are resolved in Communication Component 1.7.1:
-
The workpiece orientation information output by command 210 was incorrect.
-
In exceptional cases, “Communication Component → Deployment Settings → Mech-Interface → Listed robot” could not be selected on a new IPC.
-
The file path of the “Adapter Generator → Robot Config Eye in Hand → Robot name” parameter was incorrect.
-
The robot model obtained by Communication Component was incorrect. After the problem is fixed, if the robot models selected in Mech-Vision and Mech-Viz are different, and the Interface Service is enabled via Mech-Vision, Communication Component will obtain the robot model selected in Mech-Vision.
-
Communication Component could not be exited during the calibration process.
-
The Interface Service would be directly closed if Communication Component failed to connect with the Siemens PLC. After the problem is fixed, Communication Component will keep the Interface Service enabled and reconnect automatically.
-
Communication Component did not provide the parameter of Euler angles for STEP robots.
Communication Component 1.7.0 Release Notes
This document introduces the new features, improvements, and resolved issues of Communication Component 1.7.0.
New Features
Standard Interface and Adapter Communication No Longer Configured in Communication Component
Mech-Vision 1.7.0 now integrates the interface communication service of Communication Component. You can complete the configuration of Standard Interface and Adapter communication in Mech-Vision and do not need to use Communication Component anymore.
|
Newly Added Command 105
Communication Component 1.7.0 has added command 105 for all Standard Interface protocols (TCP/IP, PROFINET, EtherNet/IP, Modbus TCP, and Siemens PLC Snap 7). This command is used to receive the robot path output by the new “Path Planning” Step in Mech-Vision.
Newly Added Standard Interface Example Program
Communication Component 1.7.0 has added a new Standard Interface example program for ABB, FANUC, YASKAWA, KAWASAKI, KUKA, ELITE, and JAKA robots. This example program obtains the robot path output by the new “Path Planning” Step in Mech-Vision.
If you use Mech-Vision to build a solution that outputs collision-free robot paths, please load the new Standard Interface program and example programs to the robot.
Newly Added Standard Interface Programs for JAKA and ELITE
Communication Component 1.7.0 has added the Standard Interface programs for JAKA and ELITE robots. For detailed information, please refer to Standard Interface Communication – JAKA and Standard Interface Communication – ELITE.
Improvements
Modified Parameters of Commands 101 and 201
Communication Component 1.7.0 has modified the robot pose type and robot pose parameters of commands 101 and 201. Now you can input a set of pre-determined joint positions from the robot. In the ETH configuration, this set of joint positions is used as the start point for robot path planning.
Updated Master-Control Programs for ESTUN and AUBO
Communication Component 1.7.0 has updated the Master-Control programs for ESTUN and AUBO.
Improved Execution of Adapter Project
Communication Component 1.7.0 now executes the Adapter project in its original path, instead of a copy of the project in the installation directory. After modifying the Adapter project, you just need to restart the interface service to make the modifications take effect. Restarting Communication Component is no longer required.