Robot Task Commander Extensible Programming Environment
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing robotic systems face inefficiencies in task programming, particularly in networked environments with robots of varying designs and complexities, due to dedicated programming environments and the need for rewritten communication protocols with new hardware additions.
Innovation Solution
A robot task commander (RTC) system with a graphical user interface (GUI) and script engines that enables intuitive programming, distributed task planning, and communication across multiple network protocols, allowing for reusable code blocks and dynamic assignment of tasks across a network, facilitating integration with diverse robotic systems without requiring protocol-specific rewriting.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If dedicated programming environments are used for each robot, then task programming can be performed with specialized tools, but programming efficiency decreases and complexity increases when integrating multiple robots with different designs
Solution Approach 1:
The patent implements a universal programming environment that can program multiple robot types through a common interface. The system uses an abstract robot model that defines standardized communication protocols and task sequences, allowing a single programming environment to control diverse robotic systems without requiring dedicated programming tools for each robot type.
Solution Approach 2:
The patent introduces an intermediary layer consisting of abstract robot models and standardized communication protocols that mediate between the programming environment and specific robot implementations. This intermediary allows the programming environment to interact with various robot types through a consistent interface, eliminating the need for dedicated programming environments for each robot.
2Reliability
If communication protocols are rewritten for new hardware additions, then system reliability improves, but development time and productivity decrease
Solution Approach 1:
The patent defines communication protocols and task sequences in advance through abstract robot models before specific hardware is integrated. These pre-defined protocols establish standardized communication patterns that ensure reliability while eliminating the need to rewrite protocols when adding new hardware, as the abstract models already accommodate various implementations.
Solution Approach 2:
The patent separates the communication protocol definition from hardware-specific implementations by dividing the system into abstract robot models (containing protocol definitions) and concrete robot implementations. This segmentation allows protocols to be defined once at the abstract level and automatically applied to multiple hardware platforms without rewriting.
3Manufacturing precision
If expert users program tasks using specialized environments, then task execution precision improves, but ease of operation decreases for non-expert users
Solution Approach 1:
The patent uses template-based task sequences that can be copied and reused across different robots and applications. These templates encapsulate proven task execution patterns, allowing non-expert users to deploy precise tasks by simply copying and configuring templates rather than programming from scratch, thus maintaining precision while improving accessibility.
Solution Approach 2:
The patent enables task sequences to be customized through parameter adjustment rather than reprogramming. Users can modify task parameters (such as robot identifiers, target positions, or timing) to adapt standardized task templates to specific applications, maintaining execution precision while making the system accessible to non-expert users through simple parameter configuration.
Data Source
AI summary
A system for developing distributed robot application-level software includes a robot having an associated control module which controls motion of the robot in response to a commanded task, and a robot task commander (RTC) in networked communication with the control module over a network transport layer (NTL). The RTC includes a script engine(s) and a GUI, with a processor and a centralized library of library blocks constructed from an interpretive computer programming code and having input and output connections. The GUI provides access to a Visual Programming Language (VPL) environment and a text editor. In executing a method, the VPL is opened, a task for the robot is built from the code library blocks, and data is assigned to input and output connections identifying input and output data for each block. A task sequence(s) is sent to the control module(s) over the NTL to command execution of the task.