Automation Controller Software Updates via Compatible Change Instructions

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Modern automation systems require complex control software changes, which are typically time-consuming and costly due to the need for trained specialists and system downtime, and alternative methods like controller synchronization are also inefficient.

Innovation Solution

A method that allows for the efficient change of control software in automation systems by using a software participant connected via a data bus, where the controller queries and checks change instructions for compatibility, enabling automated changes without the need for complex programming or system shutdown.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Manufacturing precision

If trained specialists program the control software changes, then the control software can be changed accurately, but the process becomes time-consuming and costly with system downtime

Engineering Contradiction:
Improvecontrol software change accuracyVSAvoidsystem downtime
Core Design Contradiction:
Manufacturing precisionVSLoss of time

Solution Approach 1:

The controller automatically performs the control software change process by itself. The software participant provides the change instructions, and the controller executes them autonomously without requiring external programming intervention, thereby eliminating system downtime while maintaining change accuracy through automated validation

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The software participant prepares the control software changes in advance and stores them as change instructions. These pre-prepared instructions are then automatically transferred to and executed by the controller, eliminating the need for on-site programming and reducing system downtime

Inventive Principle:
Principle #10Preliminary action

2Ease of manufacture

If the automation system is switched off for programming changes, then the control software can be modified, but productivity is reduced

Engineering Contradiction:
Improvecontrol software modifiabilityVSAvoidsystem productivity
Core Design Contradiction:
Ease of manufactureVSProductivity

Solution Approach 1:

The controller autonomously executes the control software changes using change instructions from the software participant while remaining operational. This self-service capability allows the system to maintain productivity during the software modification process

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The software participant acts as an intermediary that provides pre-prepared change instructions to the controller. This intermediary enables the controller to perform software modifications without shutting down, as the structured change instructions guide the automated update process

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If additional controller is integrated for software changes, then software flexibility is improved, but controller complexity and synchronization requirements increase

Engineering Contradiction:
Improvesoftware flexibilityVSAvoidcontroller complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The software participant is designed as a universal component that can provide change instructions for multiple different control software scenarios. This single multi-functional component replaces the need for additional specialized controllers, maintaining software flexibility while reducing overall system complexity

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

Solution Approach 2:

The change instruction generation capability is extracted from the controller and placed in the software participant. This separation allows the controller to remain simple while the software participant handles the complexity of preparing and managing software changes

Inventive Principle:
Principle #2Taking out (Extraction)

4Manufacturing precision

If complex programming is performed by specialists, then control software changes are accurate, but the ease of operation deteriorates

Engineering Contradiction:
Improvesoftware change accuracyVSAvoidsoftware change ease
Core Design Contradiction:
Manufacturing precisionVSEase of operation

Solution Approach 1:

The system performs software changes autonomously without requiring specialist programming skills. The automated process validates and executes changes based on pre-prepared instructions, making the operation simple while maintaining accuracy through built-in validation mechanisms

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

Instead of requiring specialists to program changes from scratch, pre-prepared change instructions are copied from the software participant to the controller. This copying process eliminates complex programming operations while ensuring accuracy through the use of validated instruction templates

Inventive Principle:
Principle #26Copying

Data Source

PatentEP3948448B1Method, software terminal and system of terminals for changing control software of an automation system
Publication Date: 2022.06.22 BECKHOFF AUTOMATION GMBH
  • EP3948448B1 patent drawingFigure 1
  • EP3948448B1 patent drawingFigure 2
  • EP3948448B1 patent drawingFigure 3

AI summary

The invention relates to a method (100) for changing control software of an automation system (300), which has a controller (301) and a plurality of subscribers (303, 305, 401), one subscriber being a software subscriber (303) for changing control software of the controller (301), and the software subscriber (303) comprising a memory unit (501), in which at least one change instruction for changing the control software is stored, the method comprising: sending an individual retrieval message to the software subscriber (303) by means of the controller (301) in order to retrieve the at least one change instruction; sending a response message to the controller (301) by means of the software subscriber (303) in order to provide the change instruction; checking the at least one change instruction by means of the controller (301) as to whether the change instruction is compatible with the control software; changing the control software in accordance with the change instruction by means of the controller (301) if the change instruction is compatible with the control software; and discarding the change instruction by means of the controller (301) in a discarding step (109) if the change instruction is incompatible with the control software.