Operating Mode Control via Hierarchical Software Components
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing robotic control systems face complexity and difficulty in managing real-time switching between operating modes due to software application interdependencies, leading to unforeseen behaviors and side effects, especially as the number of modes increases.
Innovation Solution
A system and method for controlling operating modes using a hierarchical and recursive nesting of software components, with a transition sequencing module for real-time switching, implemented through a finite state machine and first-in, first-out storage for sequential transitions, ensuring consistent reconfiguration of internal wiring diagrams.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional execution sequences with conditional flip-flops are used to represent operating modes, then multiple operating modes can be implemented, but the software becomes complex and difficult to maintain due to interdependencies between components
Solution Approach 1:
The patent segments the software architecture into independent executable units called 'bricks' that can be individually activated or deactivated. Each brick represents a discrete functional component that can be independently managed, eliminating the complex interdependencies of traditional execution sequences. This segmentation allows multiple operating modes to be implemented by simply activating different combinations of bricks without increasing overall software complexity.
Solution Approach 2:
The patent implements dynamic reconfiguration of software architecture at runtime through the ability to activate or deactivate bricks on-the-fly. The system can dynamically switch between different operating modes by enabling or disabling specific bricks without requiring complex conditional logic or state machine transitions. This dynamic approach maintains simplicity while providing versatile mode switching capability.
2Adaptability or versatility
If the number of operating modes increases to provide more functionality, then system versatility improves, but the risk of side effects and unforeseen behaviors increases due to complexity of execution scheme
Solution Approach 1:
The patent implements a safety mechanism that checks for potential conflicts before activating a brick. The conflict detection unit proactively identifies incompatible brick combinations and prevents their simultaneous activation, cushioning against potential side effects before they occur. This beforehand checking ensures reliable mode switching even as the number of operating modes increases.
Solution Approach 2:
The patent incorporates feedback mechanisms through conflict detection and error handling units that monitor the system state during mode transitions. When potential conflicts are detected or errors occur during brick activation, the system provides feedback to prevent or correct the issue, ensuring reliable operation. This feedback loop maintains system reliability regardless of the number of operating modes.
3Speed
If real-time control is required for robotic systems, then response time must be minimal, but traditional software applications cannot manage mode changes in real time due to complexity
Solution Approach 1:
The patent extracts the mode switching logic from complex conditional execution sequences and implements it through simple brick activation/deactivation commands. By taking out the complexity of traditional state machine management and replacing it with direct brick control, the system achieves fast real-time mode switching without requiring complex software architecture. The simplified brick-based approach enables minimal response time for mode changes.
4Adaptability or versatility
If more software components are added to implement additional operating modes, then system functionality increases, but the difficulty of coding and maintaining the software increases
Solution Approach 1:
The patent implements universal bricks that can serve multiple functions across different operating modes. Rather than creating dedicated components for each mode, the same brick can be activated in different combinations to achieve various functionalities. This multi-functionality approach increases system capability while reducing the total number of components that need to be coded and maintained, as bricks can be reused across multiple operating modes.
Data Source
AI summary
A system and method for controlling operating modes of a system, each operating mode being implemented by an execution of one or more software components. This control system includes software components called elementary components, each elementary component having at least one input able to receive input data and/or at least one output able to transmit output data; and at least one software meta-component including one or more internal wiring diagrams, each internal wiring diagram defining interconnections between inputs and outputs of elementary components and/or meta-components, a transition logic between states defining a current state of said system and a sequence between states at least some of the states corresponding to an implementation of an internal wiring diagram, a mechanism for controlling the internal configurations, and a programming interface providing services/functions implementing at least one internal wiring scheme.