PLC Software Deployment Using Version-Compatible Package Selection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Programmable logic controllers (PLCs) face challenges in selecting the appropriate version of package programs to ensure backward compatibility with user programs, as multiple versions of programs are stored, leading to version mismatches and compatibility issues.

Innovation Solution

A control device and method that utilize a check module and package management module to select the appropriate version of package programs based on user program versions, using a package management table to ensure compatibility and facilitate flexible addition of packages.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple versions of package programs are stored in the programmable controller to support various user program versions, then the adaptability is improved, but the device complexity increases due to the need to manage and select appropriate versions

Engineering Contradiction:
Improvesupport for various user program versionsVSAvoidversion management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system performs preliminary version checking and compatibility verification before deploying package programs. The version checking unit预先 checks whether the package program version is compatible with the user program version, preventing version mismatch issues before they occur. This preliminary action simplifies the overall management by avoiding the need for complex runtime version resolution mechanisms.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

A version checking unit is introduced as an intermediary component between the package program storage and the execution unit. This intermediary automatically verifies version compatibility and prevents deployment of incompatible versions, thereby reducing the complexity of version management while maintaining support for multiple versions.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If version checking mechanisms are implemented to ensure compatibility between package programs and user programs, then the reliability is improved, but the productivity decreases due to additional checking steps in the deployment process

Engineering Contradiction:
Improvecompatibility assuranceVSAvoidsoftware deployment speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

Version compatibility checking is performed as a preliminary step before package program deployment. By checking versions in advance and only deploying compatible versions, the system ensures reliability while streamlining the deployment process. Compatible packages are deployed directly without repeated verification, maintaining productivity.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The version checking unit automatically performs compatibility verification without requiring manual intervention. The system self-manages the version checking process, comparing package program versions against user program versions and making automated decisions about deployment eligibility, thereby minimizing the impact on deployment speed.

Inventive Principle:
Principle #25Self-service

3Measurement precision

If the package management system performs comprehensive version verification, then the measurement precision of version compatibility is improved, but the loss of time increases due to detailed checking procedures

Engineering Contradiction:
Improveversion compatibility verification accuracyVSAvoiddeployment time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The version checking unit performs targeted version verification focusing on critical compatibility parameters rather than exhaustive checking of all program attributes. By checking only the essential version compatibility information stored in the storage unit, the system achieves sufficient measurement precision while minimizing the time required for verification.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentEP3936951B1Control device and software deployment method
Publication Date: 2024.05.22 OMRON CORP
  • EP3936951B1 patent drawingFigure 1
  • EP3936951B1 patent drawingFigure 2
  • EP3936951B1 patent drawingFigure 3

AI summary

A control device (100) includes: a main storage device (108) configured to store a user program and program packages (32A, 32B, 32C) in a nonvolatile manner; a main memory (106) having a package management module (106A) arranged therein; and a processor (102). The package management module (106A) performs a deployment process for selecting, from the program packages (32A, 32B, 32C), a package to be deployed based on a version of the user program, and arranging, from the package to be deployed, a version of a program compatible with the version of the user program in the main memory (106).