Modular Robot Control Architecture with Standardized I/O Blocks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Original Equipment Manufacturers (OEMs) require vendors to modify robot inputs and outputs to fit their existing I/O maps, necessitating frequent updates and changes in manufacturing processes due to varying applications and tooling configurations.

Innovation Solution

A robot system with a modular I/O map architecture that includes predefined input and output blocks, allowing applications to be dynamically placed and ordered without updating the I/O map, enabling stackable and interchangeable configurations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the I/O map is customized to fit specific applications and tooling configurations, then the robot system can be adapted to different manufacturing processes, but the I/O map requires frequent updates and changes

Engineering Contradiction:
Improveadaptability to different applications and toolingVSAvoidfrequency of I/O map updates
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The I/O map is segmented into multiple standardized blocks, each representing a specific function or device type. These blocks can be independently selected and configured without modifying the overall I/O map structure, enabling adaptation to different applications while maintaining map stability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The I/O map is designed with universal standardized blocks that can serve multiple application types. Each block contains generic input/output definitions that can be configured for different tooling and processes, allowing one I/O map to support diverse applications without requiring customizations.

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

2Adaptability or versatility

If the I/O map is updated to accommodate new applications and tooling, then the robot system can support new manufacturing processes, but the configuration time and complexity increase

Engineering Contradiction:
Improvesupport for new manufacturing processesVSAvoidconfiguration time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

Standardized blocks are pre-configured with common input/output definitions and parameters before being used in the I/O map. This preliminary preparation allows rapid deployment of new applications by simply selecting and instantiating appropriate blocks without time-consuming customization.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The I/O map configuration allows dynamic selection and arrangement of standardized blocks based on application requirements. Blocks can be easily added, removed, or reconfigured through parameter adjustments rather than structural modifications, reducing configuration time for new manufacturing processes.

Inventive Principle:
Principle #15Dynamics

3Adaptability or versatility

If different OEMs provide robots and tooling with varying I/O requirements, then the system can be customized for specific vendors, but the I/O map must be changed for each vendor combination

Engineering Contradiction:
Improvecompatibility with different OEMsVSAvoidnumber of I/O map variations
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The I/O map uses universal standardized blocks that can interface with different OEM robots and tooling through configurable parameters. The same block structure supports multiple vendor equipment types, eliminating the need for separate I/O maps for different OEM combinations.

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

Solution Approach 2:

The system accommodates different OEMs by changing parameters within standardized blocks rather than modifying the I/O map structure. Vendor-specific configurations are achieved through parameter adjustments in existing blocks, reducing the number of I/O map variations needed.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS20250332715A1Modular robot control architecture
Publication Date: 2025.10.30 RIVIAN HOLDINGS LLC
  • US20250332715A1 patent drawing
  • US20250332715A1 patent drawing
  • US20250332715A1 patent drawing

AI summary

A robot can include at least one robot component and a controller. The controller can control the at least one robot component based at least on an Input/Output (I/O) map comprising a plurality of blocks that are each associated with predefined inputs and outputs and an application associated with at least one block of the plurality of blocks, the application executes the associated predefined inputs and outputs to control the at least one robot component.