Inverter Programming via Pre-installed Code Modules

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional inverter development methods are inefficient and lack flexibility, requiring lengthy processes with high CPU load and limited customization, due to the need for step-by-step source code changes, debugging, and compilation, which results in reduced reliability and processing efficiency.

Innovation Solution

The inverter and programming device system allows for the selection and download of connection information to execute pre-installed executable code modules, eliminating the need for recompiling and re-downloading code, and enabling the creation of new function blocks for customizable applications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If source code is changed, debugged, and compiled step-by-step following development regulations, then stable quality is maintained, but development time becomes excessively long

Engineering Contradiction:
Improvequality stabilityVSAvoiddevelopment time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent pre-installs executable code modules in the inverter before runtime. These modules are prepared and tested in advance, so that during development and operation, only connection information needs to be downloaded rather than compiling entire source code sequences. This preliminary preparation eliminates lengthy compilation steps while maintaining quality through pre-tested modules.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent divides the application code into separate executable code modules that can be independently prepared and installed. Each module represents a functional segment that can be selectively executed. This segmentation allows the system to download only necessary connection information rather than recompiling entire source code sequences, significantly reducing development time while maintaining stability through modular testing.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If all executable code corresponding to an application is created and downloaded, then complete application functionality is achieved, but compilation and download time increases

Engineering Contradiction:
Improveapplication functionalityVSAvoidcompilation and download time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent extracts the connection information from the complete executable code and separates it as a distinct downloadable element. The executable code modules remain pre-installed in the inverter, and only the connection information (which is much smaller in size) needs to be downloaded to the inverter's memory. This extraction dramatically reduces download time and data transmission requirements while maintaining full application functionality.

Inventive Principle:
Principle #2Taking out (Extraction)

3Adaptability or versatility

If function blocks are always in operation state, then all functions are available, but CPU time is wasted on irrelevant processing

Engineering Contradiction:
Improvefunction availabilityVSAvoideffective processing time
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent implements dynamic execution of executable code modules based on connection information. The CPU selectively executes only those code modules that are connected and required for the current application, rather than continuously executing all installed modules. This dynamic approach maintains function availability while eliminating waste of CPU time on irrelevant processing by adapting execution to actual needs.

Inventive Principle:
Principle #15Dynamics

4Ease of operation

If source code is administered on the programming device, then flexibility in revision is achieved, but reliability decreases due to potential errors and insufficient testing

Engineering Contradiction:
Improverevision flexibilityVSAvoidcode reliability
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent pre-installs executable code modules in the inverter after they have been thoroughly tested and validated. The source code administration and compilation are performed in advance on the programming device, creating reliable executable modules. During runtime, only connection information is modified and downloaded, not the core executable code, thus maintaining both revision flexibility and reliability through pre-validation of code modules.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS7881085B2Inverter and programming device thereof
Publication Date: 2011.02.01 YASKAWA DENKI KK
  • US7881085B2 patent drawing
  • US7881085B2 patent drawing
  • US7881085B2 patent drawing

AI summary

It is possible to easily and rapidly develop an inverter application while maintaining stable quality. Executable code modules which have been sufficiently tested are installed in an inverter. An application source code is created on a programming device by using function blocks corresponding to the executable code modules and connection lines for connecting the function blocks. The source code is complied to create a connection information table for selecting the executable code modules and specifying their execution order. The connection information table is downloaded to the inverter via communication to execute the application.