PLC Label ID Management for Screen Data Consistency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In PLC systems, when label definitions are modified, the allocated memory addresses can change, leading to incorrect display of device data if the screen data is not updated accordingly, causing potential operational mistakes and inefficiencies in program development.

Innovation Solution

Implementing a system where ID information and versioning are managed to determine the necessity of re-converting and re-downloading screen data, with update rules that only change ID information when necessary, reducing the frequency of unnecessary reconversions and downloads.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If ID information is updated every time label information is corrected, then data consistency between PLC and programming apparatus is maintained, but productivity deteriorates due to unnecessary reconversion and re-download of screen data

Engineering Contradiction:
Improvedata consistencyVSAvoidprogram development efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent changes the parameter of ID information update rules from 'update every time label information is corrected' to 'update only when memory address allocation changes'. This selective parameter change maintains data consistency while avoiding unnecessary reconversion and re-download operations, thereby resolving the contradiction between reliability and productivity

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

Instead of updating ID information for all label corrections (excessive action), the patent applies partial action by updating ID information only when necessary (when memory address allocation changes). This partial update approach maintains essential data consistency while eliminating wasteful operations that reduce productivity

Inventive Principle:
Principle #16Partial or excessive action

2Manufacturing precision

If screen data is reconverted and re-downloaded every time label definitions are modified, then display accuracy is maintained, but loss of time increases due to frequent unnecessary operations

Engineering Contradiction:
Improvedisplay accuracyVSAvoidreconversion and re-download time
Core Design Contradiction:
Manufacturing precisionVSLoss of time

Solution Approach 1:

The patent changes the parameter of when screen data reconversion is triggered, from 'every label definition modification' to 'only when memory address allocation changes'. This parameter change maintains display accuracy by ensuring screen data is updated only when actually necessary, while eliminating time loss from unnecessary reconversion operations

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The patent establishes preliminary rules for determining when ID information and screen data should be updated. By pre-defining the condition (memory address allocation change) that triggers updates, the system avoids unnecessary preliminary reconversion and re-download operations, reducing time loss while maintaining display accuracy

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP2527938B1Programmable controller system and development system
Publication Date: 2018.09.19 MITSUBISHI ELECTRIC CORP
  • EP2527938B1 patent drawingFigure 1
  • EP2527938B1 patent drawingFigure 2
  • EP2527938B1 patent drawingFigure 3

AI summary

To make it possible to perform efficient program development, a development system 1 includes a label managing unit 23 configured to update, when an execution program D2 is regenerated, a label information table D3, which corresponds to the execution program D2, for generating execution screen data D5 and executes or does not execute, according to update content of the label information table D3, update of ID information associated with the label information table D3 and the regenerated execution program D2 and a drawing apparatus 3 configured to associate, when execution screen data D5 is generated based on the label information table D3, ID information of a value same as the ID information, which is associated with the label information table D3 at a point when the execution screen data D5 is generated, with the generated execution screen data D5.