Sensor Network Firmware Loading for Reliable Checking Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing checking systems face issues with firmware updates causing compatibility problems and potential device damage due to inconsistent firmware versions, leading to reliability and downtime.

Innovation Solution

A distributed checking system where each sensor unit uses a volatile memory to load the latest management application upon startup, ensuring compatibility and avoiding downtime by using a high-speed Ethernet channel and proprietary protocol for fast firmware distribution.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If firmware is updated by overwriting non-volatile memory during system operation, then firmware can be upgraded to fix bugs or add functionality, but the device may be damaged irreparably if the update is interrupted, requiring replacement of the device

Engineering Contradiction:
Improvefirmware update capabilityVSAvoiddevice reliability during update
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent divides the single non-volatile memory into two separate memory areas: a first non-volatile memory area for storing the current operational firmware and a second non-volatile memory area for storing the updated firmware. This segmentation allows the system to switch between firmware versions safely, preventing device bricking if an update fails.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent prepares a backup firmware version in advance by storing it in the second non-volatile memory area before updating the first area. This beforehand cushioning ensures that if the update process is interrupted or fails, the device can revert to the previous working firmware, preventing irreversible damage.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

2Ease of manufacture

If firmware update operation is interrupted due to power cut or disturbance, then the update process fails, but the non-volatile memory may be left in an inconsistent state causing the device to become inoperable

Engineering Contradiction:
Improvefirmware update processVSAvoidmemory inconsistency after interruption
Core Design Contradiction:
Ease of manufactureVSObject-affected harmful factors

Solution Approach 1:

By segmenting the memory into separate areas for current and updated firmware, the patent prevents memory inconsistency from affecting the entire system. If an interruption occurs during update, the first memory area remains intact and operational, while the second area can be safely discarded or reinitialized.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates a copy of the firmware in a separate memory area before performing the update. This copying mechanism ensures that the original firmware remains preserved and can be used if the update fails, preventing the device from becoming inoperable.

Inventive Principle:
Principle #26Copying

3Stability of the object's composition

If all devices in the network are forced to update firmware by overwriting non-volatile memory, then firmware version consistency is achieved, but the procedure is complex and risky requiring potential device replacement

Engineering Contradiction:
Improvefirmware version consistencyVSAvoidupdate procedure complexity
Core Design Contradiction:
Stability of the object's compositionVSDevice complexity

Solution Approach 1:

The patent implements a standardized two-area memory structure across all network devices, enabling a uniform and simplified update procedure. The management unit can update the second memory area of each device without risking the first area, reducing the need for complex verification procedures and potential device replacements.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a management unit that acts as an intermediary to coordinate firmware updates across the network. This intermediary manages the update process centrally, distributing updated firmware to the second memory areas of various devices, thereby simplifying the overall update procedure and reducing complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Ease of repair

If non-volatile memory is wiped using special hardware tools to recover a bricked device, then the device can be restored to functional state, but the device loses all functionality temporarily and requires external tools

Engineering Contradiction:
Improvedevice recovery capabilityVSAvoiddevice operational status during recovery
Core Design Contradiction:
Ease of repairVSEase of operation

Solution Approach 1:

By segmenting the memory into separate areas, the patent eliminates the need to wipe the entire non-volatile memory during recovery. If an update fails, only the second memory area needs to be cleared or reinitialized, while the first area continues to provide operational firmware, maintaining device functionality throughout the recovery process.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent enables selective discarding of the updated firmware in the second memory area when an update fails, while recovering the operational state by continuing to use the firmware in the first memory area. This selective discarding and recovering approach maintains device functionality without requiring complete memory wiping or external hardware tools.

Inventive Principle:
Principle #34Discarding and recovering

Data Source

PatentUS20250251718A1Checking system and related method for checking a production process and/or characteristics of a workpiece
Publication Date: 2025.08.07 MARPOSS SPA
  • US20250251718A1 patent drawing
  • US20250251718A1 patent drawing
  • US20250251718A1 patent drawing

AI summary

A checking system for checking a production process and/or characteristics of a workpiece is described. The checking system includes a plurality of sensor units and a network unit that are in communication with each other via a communication channel and form a network. The network unit communicates with a data processing and/or transmission entity. A checking method that enables all of the sensor units to download the most up-to-date software version each time the checking system is started up is also described.