Communication Component 1.8 Release Notes
This document introduces the new features, improvements, and resolved issues of version 1.8 of the communication component.
Communication Component 1.8.0 Release Notes
This document introduces the new features, improvements, and resolved issues of version 1.8.0 of the communication component.
| Starting from version 1.8.0, Communication Component will only run as a background communication component of the vision system when Mech-Vision or Mech-Viz is launched. Specifically, Standard Interface communication and Adapter communication should be configured in Mech-Vision, while Master-Control communication should be configured in Mech-Viz. |
New Features
New Features of Standard Interface Communication
The following features are now supported by Standard Interface communication.
-
Multiple ports and multiple DBs (data blocks) are now supported.
Application scenario: Connect multiple cameras to an IPC that communicates with an external device, enabling independent control of cameras and workstations through a single external device.
-
Communication over TCP/IP protocols supports concurrent processing of project data with a maximum of four ports. If multiple ports on the IPC are connected with the robot side, you should modify the example program to ensure that the global variables are not shared by different ports.
-
Communication over Siemens PLC Client supports concurrent processing of project data with a maximum of four DBs.
-
-
New Standard Interface commands:
-
Command 100: Trigger Mech-Vision Project and Get Results (trigger the project + switch the parameter recipe + get vision results or the planned path)
-
Command 200: Trigger Mech-Viz Project and Get Planned Path (trigger the project + set the exit port of the “Branch by Msg” Step + get the planned path)
-
Command 106: Get Gripper DO List from Mech-Vision
-
Command 111: Get Vision Move Data from Mech-Vision
-
-
Standard Interface communication now supports four-axis SCARA robots.
Compatibility with Robots
In version 1.8.0 of the communication component, robots listed in the following table are compatible with Master-Control communication and/or Standard Interface communication.
| Robot | Master-Control communication | Standard Interface communication |
|---|---|---|
Elite CS robots |
√ |
|
DENSO robots |
√ |
|
INOVANCE industrial robots |
√ |
√ |
SIASUN cobots |
√ |
√ |
TM robots (with TMFlow2 system) |
√ |
|
DOBOT CR robots |
√ |
Improvements
Updates to Standard Interface Communication
The following are the updates to the Standard Interface communication in version 1.8.0 of the communication component.
-
The example program of ABB Standard Interface communication now uses a persistent connection. You may use MM_Open_Socket or MM_Close_Socket in the main program to establish or terminate the connection.
-
The Standard Interface example programs of FANUC, KUKA, ABB, YASKAWA, and KAWASAKI are modified as follows:
-
The “lastdata” parameter is removed from the five programs, i.e., mm_get_vizdata, mm_get_visdata, mm_get_vispath, mm_get_plandata, and mm_get_dydata. Instead, the programs internally loop until all vision data is received.
-
The “resource” parameter is added to the programs mm_get_dolist and mm_get_plandata to distinguish the sources of the DO signals or Vision Move output, i.e., from Mech-Vision or Mech-Viz.
-
The mm_get_notify function is added to receive the message set in the “Notify” Step in the Mech-Vision or Mech-Viz project.
-
The mm_stop_viz function is added to stop the running of a Mech-Viz project.
-
The mm_com_test program is added to test communication.
-
Updates to Master-Control communication
The following are the updates to the Master-Control communication in version 1.8.0 of the communication component.
-
Supports setting the blend radius for Kawasaki robots.
-
Supports setting the DO signal list for AUBO robots.
-
Supports setting the DO signal list for JAKA robots.
Resolved Issues
The following issues are resolved in version 1.8.0 of the communication component.
-
Standard Interface communication
-
Resolved the issue that the communication component could not start when the IPC shut down abnormally and then restarted.
-
Resolved the issue that the height offset was not added to the pose data obtained with Command 210.
-
-
Master-Control communication
-
Resolved the issue that the velocity of linear motion could not be set for DOBOT robots in Mech-Viz.
-
Resolved the issue that the gripper could not be set for EPSON robots in Mech-Viz.
-