Comparison of application scenarios for Master-Control and Standard Interface communications


What is Master-Control?
Master-Control refers to robots being entirely controlled by the Mech-Viz software. In general, the robot itself cannot execute other frontend logic and can only passively receive and execute motion paths provided by Mech-Viz.

What is Standard Interface?
Standard Interface consists of a set of commands within the vision system. Robots or PLCs can trigger the commands and obtain standard results. Typically, the robot plays a leading role in the system, and the vision system only provides robot waypoints related to the visual aspects.

Application Scenario Comparison

Robot Communication - Robot System Integration

Master-Control: Fixed logic, no need for integration.
Standard Interface: Process logic is built on the robot or PLC. During the process, the robot or PLC triggers the vision system’s operation and receives the results calculated by the vision system. Vision system engineers need to communicate the send-receive logic with robot or PLC engineers and conduct communication tests.

Robot Communication - Robot Program Burning

Master-Control: Burn standard master-control programs following the instructions.
Standard Interface: Burn Standard Interface programs following the instructions provided.

Robot Communication - Robot Deployment and Testing

Master-Control: Only needs to test if the burning process was successful, no additional testing required.
Standard Interface: Not only needs to test if the burning process was successful, but also needs to test if the communication logic with the robot or PLC integration meets expectations.

External Device Communication - Host Computer, WCS

Master-Control: Requires integration of the vision system with the host computer and WCS, necessitating the development of an adapter.
Standard Interface: Integration of the robot or PLC with the host computer and WCS system. Typically, the vision system’s involvement is not required.

External Device Communication - Safety Circuit

Master-Control: Limited by master-control capabilities, the vision system currently does not support integration with safety circuits (remote recovery after emergency stop is not possible, teach pendant errors cannot be cleared, and there is no pause functionality). Alternatively, integration with safety circuits must be done through an adapter and interfacing with PLC, which can be cumbersome.
Standard Interface: Integration of the robot or PLC with the safety circuit. Typically, the vision system is not involved.

External Device Communication - DI (Digital Input), DO (Digital Output) Devices

Master-Control: Devices are connected to the robot, interacting with Mech-Viz software through the robot. Synchronous devices can be directly controlled using Mech-Viz, while Mech-Viz does not currently support asynchronous devices.
Standard Interface: Integration of the robot with DI, DO devices. Typically, the vision system is not involved.

Function Expansion

Master-Control: The robot’s capabilities are limited by master-control and cannot be expanded.
Standard Interface: Vision system does not intervene in the robot; the robot can expand its functionality based on its own abilities, such as conveyor line synchronization, avoiding singular points, spatial detection, etc.

Project Setup - Process Workflow

Master-Control: All process workflows need to be built in Mech-Viz.
Standard Interface: Only visual-related processes need to be set up in Mech-Viz, typically from loading bins to unloading.

Project Setup - External Device Communication

Master-Control: All external device communication logic needs to be set up in Mech-Viz.
Standard Interface: Typically, the vision system is not involved.

Optimization Delivery - Accompanied Production Testing

Master-Control: All robot-related processes must run smoothly before leaving the site. Any issues at other stages of the workstation can affect the departure time.
Standard Interface: Once the visual processes are running smoothly, the personnel can leave the site.

Skills Required If Fully Completed by the User

Master-Control: 1. Ability to interface with external devices. 2. Proficiency in Python programming when writing Adapters is required.
Standard Interface: 1. Communication integration skills. 2. Programming skills for robots (and PLCs).


Master-Control is suitable for:

  1. External Communication: Single workstation without external devices or upper-level systems.
  2. Safety Circuits: Workstations with collaborative robots and no safety light curtains, safety fences, or safety doors.
  3. Advanced Features: Master-Control capabilities meet requirements; no additional feature expansion is needed.
  4. Programming Skills: Users can do without robot programming skills, but Python programming skills are required when writing Adapters.
  5. Project Deployment: Completely user-deployed delivery, no involvement of distributors in deployment.

Standard Interface is suitable for:

  1. External Communication: Scenarios with extensive external communication and complex process logic.
  2. Safety Circuits: Requires safety light curtains, safety fences, etc. Scenarios requiring one-key recovery after emergency stop, pause, and error reporting.
  3. Advanced Features: Requires using the robot’s built-in advanced features, which are not supported by master-control.
  4. Programming Skills: Users have robot programming skills but do not know how to write adapters.
  5. Project Deployment: Visual-related processes need to be deployed and delivered by distributors.