Cross-Platform Uncrewed Control Framework for Multi-UxS Programming

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current robotic systems, such as ROS and MOOS, have a steep learning curve and lack abstraction, making them unsuitable for introductory learners, while frameworks like Scratch are too simplistic and lack complexity for advanced robotics operations. There is a need for a platform that balances abstraction and complexity to enable high-level programming and control of unmanned systems, particularly for educational and multi-UxS deployments.

Innovation Solution

The NEXUS system provides a platform-agnostic, open-source, wireless command and control framework that uses commercial off-the-shelf hardware for marine, aerial, and land-based robotic systems, allowing users to configure and control unmanned devices through a common software image and IP address, enabling programmable instructions and interactive input mappings.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Power

If ROS is used for robotic systems, then system capability and power are improved, but learning curve and ease of operation deteriorate

Engineering Contradiction:
Improvesystem capabilityVSAvoidlearning curve
Core Design Contradiction:
PowerVSEase of operation

Solution Approach 1:

The patent introduces an intermediary layer between the user and the complex ROS system. This layer provides simplified, high-level commands that abstract away the complexity of ROS, allowing users to control robotic systems without needing to understand the underlying complex framework. The intermediary translates simple user commands into the detailed ROS commands needed for system operation.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the control interface into distinct, manageable components. Instead of presenting the entire complex ROS system at once, it divides the control into modular functions and commands that can be learned and used independently. This segmentation reduces the perceived complexity and allows users to gradually build proficiency.

Inventive Principle:
Principle #1Segmentation

2Power

If ROS is used for robotic systems, then system capability is improved, but system integration complexity increases

Engineering Contradiction:
Improvesystem capabilityVSAvoidsystem integration
Core Design Contradiction:
PowerVSDevice complexity

Solution Approach 1:

The patent creates a universal interface that can control multiple different robotic systems through a common set of commands. This universal layer handles the complexity of system integration internally, allowing the same simplified interface to work across different platforms and configurations, thereby reducing integration complexity for users.

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

Solution Approach 2:

The intermediary layer acts as a mediator that manages system integration complexity. It handles the mapping between high-level commands and the specific integration requirements of different robotic systems, absorbing the integration complexity away from the user while preserving the advanced capabilities of the underlying ROS system.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Ease of operation

If Scratch is used for programming, then ease of operation is improved, but system capability and complexity deteriorate

Engineering Contradiction:
Improveease of understandingVSAvoidsystem capability
Core Design Contradiction:
Ease of operationVSPower

Solution Approach 1:

The patent implements a dynamic programming interface that can adapt to the user's skill level. For beginners, it provides simplified block-based programming similar to Scratch. As users advance, the system dynamically reveals more advanced programming capabilities and allows access to the full power of ROS, thus providing both ease of operation and system capability at different stages.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent segments the programming interface into multiple levels of abstraction. The lowest level provides simple, intuitive commands for beginners, while higher levels progressively reveal more complex capabilities. This segmentation allows users to start with ease of operation and gradually access greater system capability as they become more proficient.

Inventive Principle:
Principle #1Segmentation

4Ease of operation

If simplified frameworks like Scratch are used, then ease of operation is improved, but programming flexibility and complexity deteriorate

Engineering Contradiction:
Improveease of modificationVSAvoidprogramming flexibility
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent implements a dynamic programming model where the interface adapts to user needs. Simple, easily modifiable commands are provided for common tasks, while the underlying system maintains full programming flexibility for advanced applications. Users can easily modify high-level commands without dealing with complexity, yet retain access to full flexibility when needed.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent creates a universal programming interface that combines the ease of simplified frameworks with the flexibility of complex systems. The same interface can handle both simple modifications and complex programming tasks, providing adaptability across different user skill levels and application requirements without sacrificing either ease of operation or programming flexibility.

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

Data Source

PatentUS20230266753A1Next-Generation Cross-Platform for Uncrewed Systems
Publication Date: 2023.08.24 THE GOVERNMENT OF THE UNITED STATES OF AMERICA AS REPRESENTED BY THE SECRETARY DEPARTMENT OF HEALTH & HUMAN SERVICES
  • US20230266753A1 patent drawing
  • US20230266753A1 patent drawing
  • US20230266753A1 patent drawing

AI summary

A system having a networking device, a plurality of processing devices, and one or more unmanned devices, wherein each unmanned device couples to a corresponding one of the processing devices, wherein each unmanned device comprises one or more operational components. The system having a controller device configured to control at least one of the one or more unmanned devices via the networking device and the corresponding one of the processing devices, the controller device comprising one of the processing devices, wherein the controlled at least one unmanned device is configurable via the corresponding processing device in a control operating mode or in a robot operating mode, the control operating mode enabling the associated unmanned device to perform commands received from the controller device via the corresponding processing device, and the robot operating mode enabling the unmanned device to receive programmable instructions from the controller device via the corresponding processing device.