Refrigerant Control Software Remote Loading With Verified Updates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current software update methods for refrigerant systems require on-site technician intervention, which is time-consuming and inconvenient, necessitating equipment shutdowns.

Innovation Solution

A system that allows software updates to be downloaded remotely over the Internet, with subsequent testing to ensure successful installation, enabling verification and potential re-loading if necessary, without the need for on-site maintenance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If software updates are performed via on-site technician visits, then software can be updated, but it requires equipment shutdown and is time-consuming

Engineering Contradiction:
Improvesoftware update reliabilityVSAvoidupdate time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The refrigerant system controller performs self-diagnosis and self-testing after software updates are downloaded remotely. The system automatically executes test routines to verify software functionality without requiring on-site technician intervention, enabling the system to service itself and eliminating the need for equipment shutdown during updates.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

A remote communication interface serves as an intermediary between the refrigerant system controller and external software sources. This intermediary enables software updates to be transmitted over a network without requiring physical access to the system, allowing updates to occur while the system remains operational.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If software updates are performed remotely without testing, then update speed increases, but software functionality cannot be verified

Engineering Contradiction:
Improveupdate speedVSAvoidsoftware functionality
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system performs preliminary testing of the downloaded software before fully implementing the update. Test routines are automatically executed to verify software functionality, and only after successful verification is the update finalized. This preliminary action ensures reliability while maintaining remote update capability.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements a feedback mechanism where test results from the downloaded software are evaluated and communicated back to verify successful installation. The controller automatically assesses whether the software update was successful based on test outcomes, providing feedback that ensures functionality without requiring manual verification.

Inventive Principle:
Principle #23Feedback

3Reliability

If comprehensive test procedures are executed after software loading, then software functionality is verified, but system operation time increases

Engineering Contradiction:
Improvecontrol functionalityVSAvoidtesting duration
Core Design Contradiction:
ReliabilityVSDuration of action of moving object

Solution Approach 1:

The system executes partial test procedures that are sufficient to verify critical software functionality without performing exhaustive testing. The test routines are designed to check essential control functions rather than all possible operations, providing adequate verification while minimizing the time required for testing.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentEP2016352B1Remote software loading for refrigerant system
Publication Date: 2018.10.10 CARRIER CORP
  • EP2016352B1 patent drawingFigure 1~2

AI summary

A refrigerant system control software upgrades are remotely downloaded over information carrying media. The software upgrades can be timed to occur when the Internet traffic is low. Once the upgrade has been received, a verification test may be performed for the refrigerant system components affected by the software upgrade. The test is monitored, and the results are sent back to the remote location such that the remote location can ensure the software upgrade was successful.