Standard interface and master control adaptation schedule
Knowledge
-
Introduction
-
How to Make Sure That the Robot Controller Supports Standard Interface Communication?
-
How to Configure IP Address and Port Number in Robot Communication Configuration?
-
Why Set Host IP Address to 0.0.0.0 When Vision System Acts as Server?
-
A general introduction to IP address and port of TCP/UDP server
-
Introduction to Mech-Mind Vision's Communication via Profinet and Ethernet/IP
-
-
Operational practices
- Explanation of Common Mech-Center Logs
- Reduce project cycle time on the robot side
- Add standard interface calibration for the new robot brand and set the corresponding Euler angle convention
-
Guide for implementing standard interface programs in the background
Troubleshooting
-
How to Troubleshoot Failed Standard Interface Communications?
-
IPC
-
Standard interface
- Troubleshooting Steps for Standard Interface Failures to Trigger Mech-Viz or Mech-Vision
- Why the poses from the standard interface and Mech-Vision are differernt
- Solution for error “Number of points exceeding index”
- Result of Mech-Center Standard Interface 210 Command Planning: Anomalous Z-value in TCP Pose for Robots like FANUC
-
Errors
- Status Codes and Troubleshooting
- OSError: [WinError 10013] An attempt was made to access a socket in a way forbidden by its access permissions
- OSError: [WinError 10038] An Operation Was Attempted on Something That Is Not a Socket
- Rokae: Standard interface robot end error: Number of strings obtained by the strSplit function does not match the predefined string length.”
- KUKA Error 2135 Name not declared as subprogram
