Orthopedic Controller Configuration With Compatible Function Blocks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing orthopaedic devices, such as prostheses and orthoses, face challenges with complex and limited programming options, leading to incorrect configuration and misalignment of functionalities, which can negatively impact user safety and effectiveness.
Innovation Solution
A method for setting up a control system with a basic function block and additional function blocks, where compatibility is checked and adjusted to ensure seamless integration, using a graphical user interface for intuitive selection and combination, and an external device for computational support.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If individual parameter adjustments and programming options are provided for customization, then adaptability and versatility are improved, but device complexity and programming difficulty increase
Solution Approach 1:
The control system is divided into modular function blocks (basic function block and additional function blocks), each handling specific functionalities. This segmentation allows independent configuration of each block while maintaining overall system adaptability, reducing programming complexity through modular design.
Solution Approach 2:
Function blocks are pre-configured with predefined functionalities and parameters. The compatibility check mechanism is also pre-established, automatically verifying compatibility before integration. This preliminary preparation reduces on-site programming complexity while maintaining customization capability.
2Adaptability or versatility
If multiple additional modes and functions are added for specific activities, then adaptability is improved, but the risk of incorrect programming and misconfiguration increases
Solution Approach 1:
A compatibility check mechanism provides automatic feedback when additional function blocks are integrated. The system evaluates whether the new block is compatible with existing configurations and warns or prevents incompatible combinations, ensuring configuration accuracy while maintaining functional versatility.
Solution Approach 2:
The control system performs self-verification through automated compatibility checks. The system independently evaluates configuration validity without requiring external verification, reducing the risk of incorrect programming while maintaining adaptable functionality.
3Adaptability or versatility
If programming options are expanded for individual customization, then adaptability is improved, but ease of operation deteriorates
Solution Approach 1:
Function blocks come with pre-configured parameters and functionalities suitable for specific activities (e.g., cycling, skiing). Users can select and integrate these pre-configured blocks without manual programming of individual parameters, maintaining configuration flexibility while improving ease of operation.
Solution Approach 2:
Pre-configured function blocks serve as templates that can be copied and adapted for different applications. Instead of programming from scratch, users can replicate proven configurations and modify them as needed, reducing programming effort while maintaining adaptability.
Data Source
Figure 1~2
Figure 3~4
Figure 5~7
AI summary
The invention relates to a method for configuring a controller of an orthopedic device, which has at least one data processing device (10), sensors (20) coupled thereto and an actuator (30) which is activated and/or deactivated by the data processing device (10), the controller having a basic function block (40), in which a basic functionality of the actuator (30) is defined, a plurality of additional function blocks (60), which have different additional functionalities, being provided to an interface device (50) from a memory (15) and at least one additional function block (60) being selected and added to the basic function block (40) by way of the interface device (50), there being an interface (46) between the basic function block (40) and the at least one additional function block (60), the compatibility of the functionalities being checked and an overall functionality being generated at said interface, an adjustment of at least one functionality being carried out to establish compatibility, or an inclusion of the additional functionality being rejected, in the case of lack of compatibility at the outset.