Function Receive Send Blocks Flexible Control Program Generation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Graphical, block-based modeling of control systems is inflexible as functionalities within blocks are statically defined, making it difficult to modify or change variants of functionality.

Innovation Solution

The introduction of function receive and send blocks in a graphical modeling environment allows for flexible management of functionalities by specifying interfaces without storing the functionality itself, enabling external functionality assignment and optimization of functionality placement in the code generation process.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If functionalities are statically defined within blocks, then the model structure is simple and clear, but the flexibility to modify or change functionality variants is poor

Engineering Contradiction:
Improveflexibility to modify functionalityVSAvoidmodel structure complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the functionality into two separate blocks: a function send block that contains the actual functionality, and a function receive block that receives the functionality through a function receive port. This segmentation allows the functionality to be defined in one location while being received and used in another, enabling flexible modification without restructuring the entire model.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent extracts the functionality from the receive block and places it in a separate send block. The receive block only specifies the interface (number of inputs and outputs) without containing the functionality itself. This extraction enables the functionality to be independently modified, reused, and optimized without affecting the receiving block's structure.

Inventive Principle:
Principle #2Taking out (Extraction)

2Adaptability or versatility

If functionalities are externally assigned through function receive ports, then the adaptability and flexibility are improved, but the device complexity and interface specification requirements increase

Engineering Contradiction:
Improvefunctionality assignment flexibilityVSAvoidinterface specification complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The function receive port is designed with universal interface specifications that can accommodate different functionalities. The port only needs to define the number of inputs and outputs, which are universal parameters that work with any functionality type. This universal interface design simplifies the assignment process while maintaining high adaptability.

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

Solution Approach 2:

The function receive port acts as an intermediary between the function send block and the receiving block. It specifies the interface requirements without containing the actual functionality, serving as a mediator that enables flexible functionality assignment while maintaining clear interface contracts. This intermediary role reduces the complexity burden on both the sender and receiver.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10353363B1Function receive block, function send block, and computer-implemented method for computer-aided generation of an executable control program
Publication Date: 2019.07.16 DSPACE SE & CO KG
  • US10353363B1 patent drawing
  • US10353363B1 patent drawing
  • US10353363B1 patent drawing

AI summary

A system composed of a function receive block and a function send block for a graphical, block-based modeling environment for graphical modeling of technical and mathematical relationships with a block diagram. Blocks of the block diagram have input ports and/or output ports, wherein the blocks can be connected through their ports by signal lines for data transmission. Especially flexible management of a functionality to be implemented is achieved in that the function receive block has a function receive port through which the function receive block can be assigned a functionality and only the interfaces of the assignable functionality are specified in the function receive block in the form of the number of inputs and/or the number of outputs of the functionality. The function send block has a function send port through which a functionality is sent out to an associated function receive block.