Graphical Function Block Compiler for Memory-Limited HVAC Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Commercial HVAC control systems are becoming increasingly complex, requiring advanced control capabilities while needing to be cost-effective and adaptable to changing demands, with existing solutions struggling to efficiently utilize low-cost microprocessors for complex configurations and designs.
Innovation Solution
A function block engine system that allows for the design and implementation of control systems using software on a computer, enabling the creation of sophisticated applications with minimal memory requirements, using a compiler system that interprets meta-language and allows for flexible, modular, and adaptable control structures.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If commercial HVAC control systems use advanced control capabilities and complex configurations, then control precision and adaptability are improved, but device complexity and cost increase
Solution Approach 1:
The control system is divided into modular function blocks that can be independently configured and combined. Each function block performs a specific control task, allowing the system to be built by assembling predefined modules rather than designing complex custom control logic from scratch. This segmentation enables adaptability to different HVAC architectures while keeping individual module complexity low.
Solution Approach 2:
The control system uses universal function blocks that can operate across multiple HVAC architectures and equipment types. These function blocks are designed to be architecture-agnostic, allowing the same control logic to be deployed on different microprocessor platforms and with various HVAC equipment, thereby improving adaptability without requiring separate complex control systems for each architecture.
2Ease of manufacture
If low-cost microprocessors are used for complex HVAC configurations, then cost is reduced, but processing power and memory availability are limited
Solution Approach 1:
Control logic and algorithms are pre-compiled into optimized binary code during the software development phase. This preliminary compilation transforms high-level control specifications into efficient machine code that executes quickly and consumes minimal memory on the target microprocessor. The compilation process optimizes code size and execution speed, enabling complex control functionality to run on low-cost, memory-constrained microprocessors.
Solution Approach 2:
The system uses a compiler to create a copy of the control system software that can be transferred from the development computer to the target microprocessor. This copied software is optimized for the specific hardware platform, allowing the complex control logic to be implemented on low-cost microprocessors without requiring the original development environment or excessive memory resources on the embedded device.
3Use of energy by moving object
If sophisticated control applications are implemented with minimal memory requirements, then resource efficiency is improved, but software complexity increases
Solution Approach 1:
The system replaces interpretive or runtime compilation mechanisms with a static compilation process. Instead of using complex runtime interpretation or just-in-time compilation that would consume memory and processing resources, the control software is fully compiled beforehand into optimized machine code. This substitution of the compilation timing mechanism eliminates the need for complex runtime software components on the memory-constrained microprocessor while maintaining sophisticated control functionality.
Data Source
AI summary
A system having a graphical compiler connected to a function block engine. The graphical compiler may convert graphical information to non-graphical information. A resources allocation module may be connected to the function block engine and the compiler. Also, a function block execution list may be connected to the compiler and the function block engine. A user interface may be connected to the compiler.