Safety Controller Toolchain With Fingerprint-Based Code Consistency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing safety-related engineering systems with closed architectures and proprietary data formats face challenges in data management, flexibility, and integration of non-safety related software tools, leading to inefficiencies and increased complexity in validation and validation measures.

Innovation Solution

A method for operating a safety controller that allows program files to be stored in open text formats like XML, JSON, or TXT, with fingerprint objects ensuring data integrity and consistency checks, enabling the use of external tools and flexible management systems.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If proprietary data formats are used in closed architectures, then safety and reliability are improved, but flexibility and ease of operation deteriorate

Engineering Contradiction:
ImprovesafetyVSAvoidflexibility
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent introduces an intermediary conversion mechanism that translates between proprietary binary formats and open text formats. This mediator allows the system to maintain its secure proprietary format internally while enabling external tools and version management systems to access and manipulate the data in open formats, thus resolving the contradiction between safety (maintained through proprietary format) and flexibility (enabled through open format access).

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the data management process into two distinct parts: internal storage using proprietary binary formats for safety-critical data, and external access using open text formats for flexibility. This segmentation allows each part to optimize for its specific purpose without compromising the other, enabling both safety and flexibility to coexist.

Inventive Principle:
Principle #1Segmentation

2Reliability

If closed architectures with proprietary formats are used, then system security is improved, but integration with external tools deteriorates

Engineering Contradiction:
Improvesystem securityVSAvoidintegration capability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The conversion mechanism acts as a secure intermediary that enables external tools to work with the system without compromising security. External tools can access and modify data in open text formats, but the proprietary binary format remains the source of truth, maintaining system security while enabling tool integration.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent makes the system multi-functional by supporting both proprietary binary format (for security) and open text format (for integration). This universality allows the same system to serve both security requirements and integration needs, enabling various external tools to be incorporated without sacrificing system security.

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

3Reliability

If manual validation measures are implemented, then safety requirements are met, but time consumption and cost increase

Engineering Contradiction:
Improvesafety complianceVSAvoidvalidation time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements automated feedback mechanisms through version management systems that automatically track, validate, and verify code changes. This automated feedback loop continuously ensures safety compliance without requiring manual validation at each step, significantly reducing validation time while maintaining safety requirements.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system performs self-validation through automated processes that verify safety compliance independently. The version management system automatically checks for errors, validates changes, and ensures safety requirements are met without human intervention, eliminating time-consuming manual validation while maintaining safety standards.

Inventive Principle:
Principle #25Self-service

4Manufacturing precision

If special IT expertise and infrastructure are required, then validation quality is improved, but device complexity and operational difficulty worsen

Engineering Contradiction:
Improvevalidation qualityVSAvoidIT infrastructure complexity
Core Design Contradiction:
Manufacturing precisionVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary layer in the form of a standardized interface between the proprietary system and external version management tools. This intermediary translates complex proprietary operations into standard, widely-supported commands, allowing validation to be performed by general IT personnel using common tools rather than requiring specialized expertise in the proprietary system.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent changes the parameter of data accessibility by providing both binary and text formats. This parameter change enables the use of standard text-processing tools and version control systems that are universally understood, reducing the need for specialized IT infrastructure and expertise while maintaining high validation quality through automated processes.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS20260029769A1Method for operating a safety controller - toolchain
Publication Date: 2026.01.29 ABB (SCHWEIZ) AG
  • US20260029769A1 patent drawing
  • US20260029769A1 patent drawing
  • US20260029769A1 patent drawing

AI summary

The present disclosure provides a safety-related engineering system that allows for the integration of non-safety-related software tools. A program file and a fingerprint object associated with the program file are also provided at an update time point. A consistency check between the program file and the fingerprint object is performed at a checking time point after the update time point. At a transfer time point after the checking time point, in case the consistency check confirmed a consistency between the program file and the fingerprint object, said program file is compiled and linked to obtain an executable program code, which executable program code is transferred to a memory of a safety controller and executed by means of at least one processor of said safety controller.