Fieldbus Configuration Classes for Faster Device Parameterization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current configuration and parameterization tools, such as the TIA Portal, are overly complex and resource-intensive, making it difficult to simplify the parameterization and commissioning of decentralized peripheral devices, especially for inexperienced engineers.

Innovation Solution

An engineering station with a configuration tool and parameterization tool generates an object-oriented class with elements and functions for communication between fieldbus participants, allowing for the creation of a mesh network architecture with server and client classes, enabling bidirectional communication and simplifying the parameterization of Profinet fieldbus participants.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If comprehensive configuration tools like TIA Portal are used to parameterize fieldbus participants, then complete access to the entire digitized automation process is achieved, but the tool becomes too complex and resource-intensive for small plants and inexperienced engineers

Engineering Contradiction:
Improveaccess to automation processVSAvoidsoftware complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the fieldbus participant into two distinct types: IO controllers that execute user programs and IO devices that provide/receive process data. This segmentation allows the configuration system to apply different configuration approaches and complexity levels to different device types, reducing the overall complexity burden on users of small plants while maintaining comprehensive automation capabilities.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent inverts the traditional configuration approach by generating communication code automatically from configuration files rather than requiring manual programming. The configuration tool generates classes and code snippets that are automatically instantiated, reversing the conventional workflow where engineers manually program communication protocols. This inversion dramatically reduces the complexity and resource requirements for configuring fieldbus participants.

Inventive Principle:
Principle #13The other way round (Inversion)

2Adaptability or versatility

If manual configuration and parameterization methods are used for fieldbus participants, then flexibility in customization is achieved, but the process becomes time-consuming and error-prone

Engineering Contradiction:
Improveconfiguration flexibilityVSAvoidcommissioning time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent implements preliminary action by pre-defining communication protocols, data structures, and interaction patterns in the configuration file before actual deployment. The configuration tool generates ready-to-use code snippets and classes that encapsulate common communication scenarios, allowing engineers to configure fieldbus participants quickly without manual programming of communication logic. This preliminary preparation significantly reduces commissioning time while maintaining flexibility through configurable parameters.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent uses copying by generating reusable code templates and class definitions that can be instantiated multiple times with different parameters. Instead of manually configuring each fieldbus participant from scratch, the system creates master templates that are automatically copied and adapted to specific devices, reducing both time and errors while preserving flexibility through parameter customization.

Inventive Principle:
Principle #26Copying

3Adaptability or versatility

If decentralized peripheral devices are parameterized using traditional methods, then device functionality is achieved, but the parameterization process remains difficult and complex

Engineering Contradiction:
Improvedevice functionalityVSAvoidparameterization ease
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent implements self-service by enabling decentralized peripheral devices to automatically receive and apply their configuration parameters through automated code generation and instantiation. The configuration tool generates device-specific code that is automatically loaded onto IO devices, eliminating the need for manual parameterization at the device level. This self-service approach maintains full device functionality while dramatically improving parameterization ease for inexperienced engineers.

Inventive Principle:
Principle #25Self-service

Data Source

PatentEP3855260B1Method for configuring and parametrizing field bus users and engineering system
Publication Date: 2023.03.01 SIEMENS AG
  • EP3855260B1 patent drawingFigure 1
  • EP3855260B1 patent drawingFigure 2
  • EP3855260B1 patent drawingFigure 3

AI summary

The invention relates to a method for configuring and parameterizing fieldbus participants (Ctr, Dev) that are interconnected via a fieldbus (F), wherein at least one first fieldbus participant (Dev) is configured to provide and/or receive process data (IO), and a second fieldbus participant (Ctr) is configured to execute a user program (AP), wherein in a first step (S1) a topology (Topo) with configuration parameters (CP) of the fieldbus participants (Ctr, Dev) is defined in a configuration file (CD) using a configuration tool (CT), and in a second step (S2) the first fieldbus participant (Dev) is parameterized for subsequent communication via the fieldbus (F) with at least one configuration data record (Dconf) comprising at least a first part (CD1) of the configuration file (CD), and wherein in a third step (S3) the configuration file (CD) and further code parts (C1, ...) are used to create a new configuration file (CD).,C5) from a program library (PB) an object-oriented class (class) with elements (E) and functions (f) for communication between the second fieldbus participant (Ctr) and the first fieldbus participant (Dev) is generated, wherein in a fourth step (S4) the class (class) is instantiated in the user program (AP) of the second fieldbus participant (Ctr) and during the execution of the user program (AP) the functions (f) are used for communication, thereby enabling access (Z) to the process data (IO).