PLC EEPROM Recovery Using Section Checksums for EtherCAT Slaves

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for recovering EEPROM data in EtherCAT networks are ineffective in automatically detecting and correcting errors, often treating all modifications as errors regardless of cause, leading to communication failures between master and slave devices.

Innovation Solution

A method using a PLC communication module to analyze EEPROM data section-wise checksums, compare them with original data stored in read-only permanent memory, and inform users of mismatches, allowing for automatic recovery and notification of corrected sections.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual recovery methods are used for EEPROM data errors, then data can be recovered through dedicated programs or hardware replacement, but the process is time-consuming and requires human intervention

Engineering Contradiction:
ImproveEEPROM data accuracyVSAvoidrecovery time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs automatic self-diagnosis and self-recovery of EEPROM data errors. The PLC communication module automatically detects checksum mismatches, identifies erroneous data sections, and recovers correct data from backup storage without requiring manual intervention through dedicated programs or hardware replacement.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system stores backup EEPROM data in read-only permanent memory before normal operation. When data errors occur, the pre-stored backup data is immediately available for recovery, eliminating the need for time-consuming manual data re-download or hardware replacement.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If all EEPROM modifications are treated as errors, then data integrity is maintained, but legitimate configuration changes cannot be made

Engineering Contradiction:
ImproveEEPROM data integrityVSAvoidconfiguration flexibility
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The EEPROM data is divided into multiple sections, each with its own checksum. The system compares checksums section-by-section to identify only the specific erroneous sections rather than treating the entire EEPROM as corrupted. This allows selective recovery of only the affected sections while preserving legitimate changes in other sections.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system provides feedback to users about detected EEPROM errors and recovery actions. Users can review error reports and approve or modify recovery operations, allowing them to distinguish between genuine errors and legitimate configuration changes before automatic recovery is executed.

Inventive Principle:
Principle #23Feedback

Data Source

PatentEP3660722B1Method for recovering eeprom of slave device by PLC communication module
Publication Date: 2021.09.29 LSIS CO LTD
  • EP3660722B1 patent drawingFigure 1
  • EP3660722B1 patent drawingFigure 2
  • EP3660722B1 patent drawingFigure 3

AI summary

Disclosed is a method for recovering, by a programmable logic controller (PLC) communication module, data in an electrically erasable programmable read-only memory (EEPROM) storing configuration information of a slave device, the method being characterized in that the method includes: (A) analyzing original data of the EEPROM on a data section basis to compute a checksum of each data section, wherein the original data is stored in the PLC communication module; (B) analyzing EEPROM data read from the EEPROM on a data section basis to compute a checksum of each data section, wherein the EEPROM is attached to a an EtherCAT slave controller (ESC) of the slave device; (C) comparing each section-based checksum of the original data with each section-based checksum of the EEPROM data; (D) when at least one of section-based checksums mismatches between the original data and the EEPROM data, detecting at least one section having the at least one checksum having the mismatching, and indicating a flag value corresponding to the mismatching into the at least one section of the EEPROM data; and (E) informing a user of the at least one section of the EEPROM data having the flag value corresponding to the mismatching.