Robotics Programming Interface for Semiconductor Manufacturing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current simulation technologies lack effective real-time access and integration with physical systems, particularly in complex electromechanical systems like manufacturing robotics, hindering design, purchase, and deployment processes.

Innovation Solution

A programming interface that includes an embedded layer for physical hardware access, a simulation system, and a diagnostics engine for real-time comparison and analysis, allowing simultaneous access to both simulation and physical control tools.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If simulation tools are provided to physical system users, then access to simulation technologies is improved, but integration with physical systems in real-time remains insufficient

Engineering Contradiction:
Improveaccess to simulation technologiesVSAvoidreal-time integration with physical systems
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent introduces an embedded layer as an intermediary component that bridges the simulation system and physical hardware. This embedded layer enables real-time data exchange and coordination between the simulation environment and actual robotic systems, allowing simulation tools to be effectively integrated with physical systems while maintaining real-time operational reliability.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The programming interface is designed to be universal, supporting both simulation control and physical system control through a unified API. This multi-functional interface allows the same programming interface to access and control both simulated and physical robotic systems, improving ease of operation while maintaining real-time integration capabilities.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Productivity

If simulation and physical control tools are accessed simultaneously, then real-time diagnostic and control capabilities are improved, but system complexity increases

Engineering Contradiction:
Improvereal-time diagnostic and control capabilitiesVSAvoidsystem architecture
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system is segmented into distinct functional layers: a simulation system, a physical hardware system, and an embedded layer that coordinates between them. This segmentation allows simultaneous access to both simulation and physical control tools while managing complexity through modular architecture, where each layer handles specific functions independently.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The embedded layer serves as a mediator that manages the complexity of simultaneous access to simulation and physical systems. By introducing this intermediary component, the system can provide real-time diagnostic and control capabilities without exposing the full complexity of dual-system coordination to the user, as the embedded layer handles the complex integration tasks.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Measurement precision

If feedback data from simulation and physical systems is compared in real-time, then measurement precision is improved, but computational requirements increase

Engineering Contradiction:
Improvefeedback data comparison accuracyVSAvoidcomputational resources
Core Design Contradiction:
Measurement precisionVSUse of energy by moving object

Solution Approach 1:

The diagnostics engine implements partial comparison of feedback data by focusing on critical parameters and key differences between simulation and physical system outputs. Rather than performing exhaustive comparisons of all data points, the system selectively analyzes the most relevant parameters, achieving sufficient measurement precision while reducing computational resource requirements.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS7890194B2Robotics programming interface
Publication Date: 2011.02.15 BROOKS AUTOMATION US LLC
  • US7890194B2 patent drawing
  • US7890194B2 patent drawing
  • US7890194B2 patent drawing

AI summary

A programming interface for a hardware system includes an embedded layer for programmatic access to a physical realization of hardware, a simulation system for simulation of the hardware, and a diagnostics engine that analyzes and compares feedback data from the simulation system and the physical realization. The programming interface may be usefully employed, for example, in the design, purchase, and deployment of robotics for semiconductor manufacturing.