Method for automatically generating hvac digital simulation system based on topology synchronization

Abstract

The application discloses a kind of based on topological synchronous heating ventilation air conditioner digital simulation system automatic generation method, by real-time monitoring topological graph drawing window's editing save operation, identify change content, generate change list and execute the following update of digital simulation system.The present application ensures that the current simulation system and design change are consistent, avoids in the process of the establishment adjustment of heating ventilation air conditioner system design change forgets to execute simulation system update, leading to simulation system and actual layout structure produces deviation, simulation verification result loses reference value, control logic is issued to wrong equipment node and the like defects.

Description

Technical Field

[0001] This invention relates to the field of digital simulation technology for HVAC systems, and specifically to an automatic generation method for HVAC digital simulation systems based on topology synchronization. Background Technology

[0002] In modern public buildings, centralized HVAC systems are typically installed to control indoor temperature. To facilitate monitoring and control of these systems, a digital simulation system is usually required. Existing HVAC digital simulation systems typically involve two steps: first, drawing a topology diagram of the system, including equipment layout and connections; and then, establishing corresponding equipment objects and data links within the simulation system based on the topology diagram. In current technology, these two steps are often separated, which has the following shortcomings: First, the topology diagram and the simulation system construction process are disconnected. Users need to draw the topology diagram in the drawing tool first, and then manually create the corresponding devices, configure the points, and establish the connection relationships in the simulation platform one by one. This work is repetitive and prone to errors.

[0003] Secondly, during the system design and assembly process, it is sometimes necessary to adjust or modify system components or layout structures (such as adding or deleting devices, or modifying connection relationships). While these adjustments can be easily made using drawing tools, the digital simulation system cannot automatically update after the topology diagram is modified. Therefore, when system design changes, users not only need to manually modify the topology diagram but also make corresponding modifications one by one in the simulation system. This is inefficient and prone to omissions, resulting in a final topology diagram that is inconsistent with the simulation system.

[0004] Third, there is a lack of a rapid construction channel from topology diagrams to simulation systems. Some existing configuration software supports the mapping from graphic elements to data objects, but most are limited to specific industrial scenarios (such as substations, power systems, etc.). There is a lack of a general method for HVAC systems that can call on the object model to quickly complete the construction of a digital simulation system, and there is also a lack of a mechanism that automatically triggers the synchronous update of the simulation system after the topology diagram is modified.

[0005] Fourth, the topology diagram is often adjusted and changed during the system construction phase. If the user forgets to update the simulation system, the simulation system will deviate from the actual system structure, which will seriously affect the accuracy of subsequent equipment debugging, simulation verification and control logic distribution based on the simulation system. In severe cases, it may even cause control errors or abnormal operation of field equipment. Summary of the Invention

[0006] To address the shortcomings of the existing technologies, the technical problem this invention aims to solve is: how to provide a more efficient and accurate method for automatically generating a topology-synchronized HVAC digital simulation system, ensuring that the digital simulation system generated during the simulation system construction process maintains a strict correspondence with the currently adjusted layout of the HVAC system, avoiding asynchrony that could lead to deviations between the simulation system and the actual system structure. This would affect the accuracy of subsequent equipment debugging, simulation verification, and control logic deployment based on the simulation system, and in severe cases, could even cause control errors or operational abnormalities in the field equipment.

[0007] The digital simulation system in this invention refers to a virtual system built based on object models and algorithm models, capable of simulating and replicating the operating state of HVAC systems in digital space. It includes equipment objects, point data, algorithm logic, and data links. The configuration topology diagram (i.e., topology structure diagram) is a schematic diagram of the HVAC system structure built by the user in a graphical drawing window by dragging and dropping equipment elements and connecting lines. It is used to express the connection relationships between equipment and the data flow. Topology synchronization update means that when the user edits or modifies the configuration topology diagram, the system automatically detects the changes and synchronizes them to the constructed digital simulation system, ensuring consistency between the digital simulation system and the configuration topology diagram.

[0008] To solve the above-mentioned technical problems, the present invention adopts the following technical solution: A method for automatically generating a digital simulation system for HVAC based on topology synchronization includes the following steps: S1 first completes the drawing of the current HVAC configuration topology in the topology drawing window, and then builds the corresponding digital simulation system based on the current HVAC configuration topology, forming a historical record; Its characteristic is that it further includes: S2 monitors the editing and saving operations of the topology drawing window in real time. When an editing and saving action is detected in the topology drawing window, a synchronous detection process is executed. The synchronous detection process includes: comparing the current structured data of the topology with the structured data of the topology recorded when the simulation system was built most recently, and identifying the changed content. The comparison uses the following matching rules: A unique identifier is pre-assigned to all different elements in the topology diagram. The unique identifier of the configured topology diagram element is used as the primary matching key. If an element identifier exists in both the current topology diagram and the historical record, and the associated object model / algorithm model identifier is consistent, it is determined to be "unchanged". If an element identifier exists in both the current topology diagram and the historical record, but the associated model identifier is inconsistent, it is determined to be "attribute changed", and all elements with changed attributes are added to the change item list. If an element identifier exists in the current topology diagram but not in the historical record, it is determined to be "added", and all newly added elements are added to the new item list. If an element identifier exists in the historical record but not in the current topology diagram, it is determined to be "deleted", and all deleted elements are added to the deletion item list. If the start or end point of a connection relationship changes, it is determined to be "connection changed", and all elements belonging to the connection change are added to the connection change item list. S3 generates a change list based on the comparison results. The change list includes the list of new items, the list of deleted items, the list of changed items, and the list of connection change items. S4 automatically performs follow-up updates to the digital simulation system based on the change list: For the operation of the new item list: based on the object model or algorithm model associated with the new graphic element, create the corresponding device instance or algorithm instance in the digital simulation system, and establish the corresponding data link according to the connection relationship in the topology diagram; For the deletion list operation: based on the association index between the deleted graphic element and the simulation system element, delete the corresponding device instance or algorithm instance and its related data link in the digital simulation system; For the change item list operation: based on the object model or algorithm model after the element replacement, update the definition of the corresponding device instance or algorithm instance in the digital simulation system; For operations on the connection change list: based on the changes in the connection relationships of elements in the topology diagram, add, delete, or modify the corresponding data links in the digital simulation system; After the S5 update is complete, it saves the current topology diagram and the corresponding updated digital simulation system as a new history. It also updates the association index between the configuration topology diagram and the digital simulation system to ensure they remain consistent, and further writes the update results to the synchronization log. Furthermore, if anomalies occur during synchronization (such as missing object models, algorithm incompatibility, data link conflicts, etc.), the system records the anomaly information and marks the corresponding changes for subsequent user verification and processing.

[0009] In this way, this method enables the design platform to automatically detect changes and execute the simulation system to update accordingly when the user adjusts or modifies the topology diagram. This ensures that the topology diagram and the simulation system are always consistent, thus avoiding defects such as deviations between the simulation system and the actual layout, loss of reference value of simulation verification results, and control logic being sent to the wrong device nodes when the topology diagram has been adjusted or modified during the assembly and adjustment of the HVAC system.

[0010] Furthermore, the process of drawing the current HVAC configuration topology diagram in S1 includes the following sub-steps: S1.1 Drag and drop the equipment elements required for the current design of the HVAC system from the equipment element library to the drawing canvas to generate the corresponding equipment element nodes. Each equipment element node is automatically associated with the corresponding object model. S1.2 Drag and drop the required external algorithm primitives from the algorithm primitive library onto the drawing canvas to generate corresponding algorithm primitive nodes. Each algorithm primitive node is automatically associated with the corresponding external algorithm model. S1.3 Draw connecting lines between device element nodes and algorithm element nodes using a connecting tool to establish data flow relationships. The data flow relationships specifically include: the data source relationship between device element output points and algorithm element input ports, and the data target relationship between algorithm element output ports and device element input points. After completing all drags and drops and connections in S1.4, the current HVAC configuration topology diagram is completed. The configuration topology diagram automatically records the corresponding structured data, including the equipment element list (the object model identifier associated with each element), the algorithm element list (the algorithm model identifier associated with each element), and the connection relationship list (the start and end identifiers of each connection line).

[0011] This method uses a graphical drag-and-drop interface and connecting lines to represent the equipment composition, algorithm configuration, and data flow relationships of an HVAC system. This graphical representation is then automatically converted into structured data, achieving a transformation from a "user-operable graphical interface" to "computer-parsable structured data." Users do not need to manually write any configuration files or code; they can simply use intuitive drag-and-drop operations to digitally define the topology of the HVAC system. This definition is accurately recorded by the system in a structured form, providing a complete data foundation for the system to automatically call the object model and algorithm model to complete the simulation system construction in subsequent steps. This effectively avoids errors and omissions caused by manual configuration and lowers the technical threshold for building digital simulation systems.

[0012] Furthermore, the construction of the corresponding digital simulation system based on the current HVAC configuration topology diagram in S1 includes the following sub-steps: S1.5 sends a command to the design platform to build a digital simulation system by using the "Build Simulation System" button (or a similar triggering method) in the drawing window; The S1.6 design platform responds to the command by reading the structured data of the current configuration topology diagram, retrieving the corresponding object models from the object model library one by one according to the device element list, and creating the device instance corresponding to the digital simulation system; retrieving the corresponding algorithm model from the algorithm repository one by one according to the algorithm element list, and creating the corresponding algorithm instance in the digital simulation system; and establishing the data link between the device instance and the algorithm instance according to the connection relationship list to form the corresponding digital simulation system. The S1.7 design platform archives the completed digital simulation system as a project file, which contains structured data including a list of device instances, a list of algorithm instances, data link configurations, and a topology diagram.

[0013] This method achieves automatic mapping from structured data in the configuration topology diagram to a runnable simulation system: the system parses the structured data and retrieves the corresponding complete object model definition from the object model library based on the object model identifier in the device primitive list, creating the corresponding device instance in the simulation runtime space; it retrieves the corresponding algorithm definition from the algorithm repository based on the algorithm model identifier in the algorithm primitive list, creating the corresponding algorithm instance; and it establishes the data link between the device instance and the algorithm instance based on the start and end identifiers recorded in the connection relationship list. After the user completes the topology diagram drawing, a single click is all it takes for the system to automatically create all device instances, algorithm instances, and data links in the simulation system, eliminating the need for manual configuration by the user. This achieves one-click rapid construction from "graphical design" to "runnable simulation system," significantly improving the construction efficiency of digital simulation systems.

[0014] Furthermore, S1 also includes: The S1.8 design platform establishes an association index between the configuration topology diagram and the digital simulation system, binding the unique identifier of each element in the topology diagram with the identifier of the corresponding device instance / algorithm instance in the simulation system, so that there is a one-to-one mapping relationship between the elements of the topology diagram and the elements of the simulation system.

[0015] Thus, this method, based on the completion of the simulation system construction, further establishes a one-to-one mapping relationship between configuration topology diagram elements and simulation system elements. The specific function of this association index is: when the user subsequently edits or modifies the topology diagram, the system can quickly locate the corresponding device instance or algorithm instance in the simulation system through the unique identifier of the element, thereby accurately performing subsequent follow-up update operations and ensuring that the topology diagram and the simulation system always remain consistent. This association index provides data support for the bidirectional mapping between the topology diagram and the simulation system, and is the technical guarantee for the subsequent automatic synchronization update mechanism.

[0016] Furthermore, this method is based on a design platform for building a digital simulation system for HVAC. The design platform includes a digital simulation system framework building module (used to draw the configuration topology diagram, establish the mapping relationship between the external algorithm model and the object model points, and generate a digital simulation system framework based on the configuration topology diagram), an object model instantiation module (to realize the initial construction of the digital simulation system and complete the instantiation), and a digital simulation system instance update module (to realize the follow-up update of the digital simulation system). The digital simulation system framework building module has a topology drawing window, which includes a device drag-and-drop sub-window connected to the object model library, an algorithm drag-and-drop sub-window connected to the algorithm repository, a data connection drawing sub-window, and an execution order configuration sub-window. The device drag-and-drop sub-window is used to display a list of all available object models in the object model library, and to receive user drag-and-drop operations to generate corresponding device elements on the construction canvas (the construction canvas refers to the main interface of the topology drawing window). Each device element carries a complete list of points of the corresponding object model. The algorithm drag-and-drop sub-window is used to display a list of all available external algorithm models in the algorithm repository, and to receive user drag-and-drop operations to generate corresponding algorithm primitives on the construction canvas. Each algorithm primitive carries a corresponding input-output mapping relationship. The data connection drawing sub-window is used to receive the user's connection operation between the device graphic elements and the algorithm graphic elements to complete the drawing of the configuration topology diagram (i.e. to realize the graphical construction of the digital simulation system framework), establish the data source relationship between the output point of the object model and the input port of the external algorithm model, as well as the data target relationship between the output port of the external algorithm model and the input point of the object model, and record the start point and end point of each connection to form a data mapping relationship list. The execution order configuration sub-window is used to receive the user's execution priority settings for each algorithm primitive and form an execution order list; The digital simulation system framework building module also has a structured data export unit connected to the topology drawing window, which is used to read the list of all device primitives, algorithm primitives, data mapping relationship list and execution order list on the building canvas, and serialize them into JSON or XML format structured framework data, which serves as the configuration basis for subsequent steps. The object model instantiation module has a structure framework import window, a device instantiation window, and a data link establishment window. The structural framework import window is used to connect with the structured data export unit of the digital simulation system framework building module, receive and parse the structural framework data, extract the device list, algorithm list, data mapping relationship list and execution order list, and parse it into system instantiation configuration data. The device instantiation window is connected to the structural framework import window. It is used to establish a connection with the object model library one by one according to the parsed device list, read the object model definition corresponding to each device, create the corresponding device instance object in the system, and assign a unique instance identifier to each device instance. Furthermore, the device instantiation window is also used to initialize all points (including input points, output points, and mechanism supplement points) of each device instance in the runtime data space, so that the device instance enters the "runnable device object" state from the "object model definition" state. The data link establishment window is connected to the device instantiation window and is used to establish the following data links one by one according to the parsed data mapping relationship list: establishing a data acquisition mapping between the input points of each device instance and the corresponding physical sensor data source; establishing a control mapping between the output points of each device instance (including the native output points of the object model and the mechanism supplementary points) and the corresponding physical actuator control address; associating the input port of the algorithm instance with its data source point; and associating the output port of the algorithm instance with its data target point. This completes the construction of the required digital simulation system and saves its topology structured data to a connected historical record management unit. Furthermore, the data link establishment window is also used to read and apply the execution order list, write the execution priority of each algorithm instance into the scheduler's configuration, and enter the running phase.

[0017] The digital simulation system instance update module includes a topology change monitoring unit, a change detection and comparison unit, and a follow-up update execution unit.

[0018] The topology change monitoring unit is connected to the topology drawing window and is used to monitor in real time the editing and modification operations performed by the user on the saved configuration topology in the topology drawing window. The editing and modification operations include, but are not limited to: adding device elements, deleting device elements, modifying device element attributes (including changing associated object models), adding algorithm elements, deleting algorithm elements, and modifying connection relationships. Whenever the user completes an editing action, the topology change monitoring unit automatically triggers the change detection and comparison unit to start.

[0019] The change detection and comparison unit is connected to the topology change monitoring unit, the topology drawing window, and the history management unit, respectively. Upon receiving a trigger signal from the topology change monitoring unit, it reads the structured data of the current topology from the topology drawing window and compares it with the structured data of the historical topology saved during the most recent construction of the digital simulation system, read from the history management unit, to identify changes. The comparison uses the unique identifier of the element as the primary matching key and is determined according to the following rules: if the element identifier exists in both the current topology and the history, and the associated object model or algorithm model identifier is consistent, it is determined as "no change"; if the element identifier exists but the associated model identifier is inconsistent, it is determined as "attribute change"; if the element identifier exists in the current topology but not in the history, it is determined as "added"; if the element identifier exists in the history but not in the current topology, it is determined as "deleted"; if the start or end identifier of a connection relationship changes, it is determined as "connection change". The change detection and comparison unit generates a change list based on the determination results, which includes a list of added items, a list of deleted items, a list of attribute change items, and a list of connection change items.

[0020] The follow-up update execution unit is connected to the change detection and comparison unit and is used to automatically execute follow-up update operations of the digital simulation system according to the change list. Its specific execution logic is as follows: For "Added" items in the change list, based on the object model or algorithm model identifier associated with the newly added graphic element, the corresponding definition is retrieved from the object model library or algorithm repository, and a corresponding device instance or algorithm instance is created in the simulation system. A corresponding data link is established based on the connection relationship in the topology diagram. For "Deleted" items, based on the association index between the deleted graphic element and simulation system elements, the corresponding device instance or algorithm instance and its associated data link are deleted in the simulation system. For "Attribute Change" items, based on the object model or algorithm model identifier after the graphic element is replaced, the definition of the corresponding device instance or algorithm instance is updated in the simulation system. For "Connection Change" items, based on the changes in the connection relationship in the topology diagram, the corresponding data link is added, deleted, or modified in the simulation system. If the follow-up update execution unit encounters an anomaly (including missing object models, algorithm incompatibility, or data link conflicts) during the update operation, it records the anomaly information and skips the change item, continuing to execute subsequent change items.

[0021] The historical record management unit is also connected to the follow-up update execution unit. After the follow-up update execution unit completes its update operation, it saves the structured data of the current topology diagram and the corresponding digital simulation system configuration as a new historical record, and updates the association index between the configured topology diagram and the digital simulation system, ensuring that the one-to-one mapping between topology diagram elements and simulation system elements remains up-to-date. Furthermore, the historical record management unit is also used to store synchronization logs, which include timestamps of each synchronization operation, change list content, follow-up update execution results, and exception information.

[0022] This design allows the platform to automatically detect the topology drawing status and automatically update and generate a new HVAC digital simulation system. This ensures that the current simulation system is consistent with the design changes and avoids defects such as forgetting to update the simulation system after design changes during the assembly and adjustment of the HVAC system, which can lead to deviations between the simulation system and the actual layout, loss of reference value of simulation verification results, and control logic being sent to the wrong equipment nodes.

[0023] Furthermore, the design platform also includes a material model building module, a material model library, an algorithm building module, an algorithm repository, and a mechanism algorithm binding module; The object model building module is used to create, edit, and store object models; the object model library is used to store all the object models that have been built; the algorithm building module is used to create, store, and verify mechanism algorithms and external algorithm models; the algorithm repository is used to store all the mechanism algorithms and external algorithm models that have been built; and the mechanism algorithm binding module is used to bind object models and mechanism algorithms, configure scene matching rules, and verify binding relationships. Specifically, the structure of each module is as follows: (a) Object Model Construction Module The object model building module provides an object model editor with an editing input window, allowing users to interactively complete the following data input operations: filling in equipment metadata information (including brand, model, equipment type, and version); adding equipment input point definition information, including point name, data type, numerical range (minimum / maximum value), unit, and description; adding equipment output point information, including point name, data type, numerical range (minimum / maximum value), unit, and description; and adding equipment design parameter information, including rated power, rated flow rate, design temperature, and design pressure. After the data output operation is completed, the object model building module serializes the object model data in JSON or XML format and stores it in the object model library.

[0024] (ii) Object Model Library The object model library is implemented using a relational database or a document-oriented database to store all constructed object models. The storage structure of each object model includes: a unique model identifier, equipment metadata (brand, model, equipment type, version), a list of input points (each point includes name, data type, minimum value, maximum value, unit, and description), a list of output points (each point includes name, data type, minimum value, maximum value, unit, and description), a list of design parameters (parameter name, value, and unit), creation time, modification time, and version number. The object model library has a search window associated with each stored object model (for searching and retrieving object models) and a add / delete / modify window (for modifying object model data).

[0025] (III) Algorithm Construction Module The algorithm construction module includes an algorithm editor that allows users to programmatically construct physical mechanism algorithms. The algorithm editor has an algorithm code input window, which embeds a preset algorithm template that the user's input algorithm code must follow. The algorithm template defines the declaration format of the algorithm's input parameters, output parameters, and adjustable parameters. The algorithm construction module also has a syntax checking unit connected to the algorithm code input window. This unit performs syntax checks on the input code and verifies the algorithm code by calling a compiler or interpreter, checking whether the input and output parameters are completely declared and identifying missing or redundant definitions. The algorithm construction module also has an algorithm verification unit connected to the syntax checking unit. After the syntax check passes, the verification unit calls a preset standard test dataset to test and verify the algorithm, comparing the algorithm's calculation results with preset standard values. If the deviation is within the allowable range, the verification is marked as successful. The verification unit also has an output terminal connected to an algorithm repository, used to store verified algorithms in the algorithm repository, with the status marked as "verified."

[0026] The algorithm building module also supports the storage of physical mechanism calculation code and external algorithm models required for control, implemented in programming languages ​​(including but not limited to Python, C++, and Java).

[0027] (iv) Algorithm repository The algorithm repository employs the same data storage technology as the object model library, serving as a database for storing all constructed mechanistic algorithms and external algorithm models. The algorithm repository includes an algorithm storage unit connected to the output of the algorithm construction module, used to receive algorithm data, index it according to algorithm type and applicable device type, and then store it in the database. The algorithm repository also includes a search operation window connected to the algorithm storage unit, used to receive user search commands, perform searches by name, version, device type, and algorithm type, and display the results. Furthermore, it may include a version management unit connected to the algorithm storage unit, used to save historical versions of each algorithm record and support version rollback.

[0028] (v) Mechanism Algorithm Binding Module The mechanism algorithm binding module has an algorithm binding configuration window, which includes a physical model point display sub-window and an available algorithm display sub-window. The physical model point display sub-window is used to establish a connection with the physical model library, read and display the complete point list of the currently selected physical model. The available algorithm display sub-window is used to establish a connection with the algorithm repository, display the list of available mechanism algorithms with the status "verified" in the algorithm repository, and receive the user's binding selection command to establish an association record between the algorithm and the physical model. The mechanism algorithm binding module also has an automatic mapping relationship generation unit connected to the algorithm binding configuration window, which is used to automatically generate input parameters based on the algorithm's input parameter list and the physical model's input point list after the user completes the algorithm selection. The system includes a mapping relationship table and an output parameter mapping relationship table automatically generated based on the algorithm's output parameter list and the object model's output point list. The mechanism algorithm binding module also has a mechanism supplementary point creation unit connected to the automatic mapping relationship generation unit. This unit automatically creates mechanism supplementary point definitions in the object model's output points after the output mapping relationship table is generated, and records their associated algorithm identifiers and mapping relationships. The mechanism algorithm binding module also includes a scene matching rule configuration window, which receives the corresponding mechanism algorithms specified by the user for different running scenarios and stores the matching conditions in the form of a rule table. Finally, it includes a binding relationship verification unit connected to the mechanism supplementary point creation unit, which simulates algorithm calls using preset test data after binding is completed to confirm that the data can flow correctly.

[0029] Therefore, the aforementioned platform can be used to quickly and efficiently generate a digital simulation system for HVAC systems. This generated system can simulate and reproduce the actual working scenarios of HVAC systems in real time, and can automatically run internal system mechanism algorithms and external control algorithms, greatly improving the system's automatic control effect. Furthermore, the generated digital simulation system can automatically update along with the topology diagram during the adjustment of air conditioning system components. This avoids the tedious work of manually modifying each device instance, data link, and algorithm configuration in the simulation system during component adjustments, as well as the inconsistency between the simulation system and the actual system structure caused by untimely manual modifications or operational errors, ensuring that the simulation system always remains synchronized with the actual design.

[0030] The present invention has the following beneficial effects.

[0031] 1. Enables one-click rapid construction from configuration topology diagrams to digital simulation systems. After users complete the topology diagram by dragging and dropping device and algorithm elements, the system automatically calls the object model and algorithm model to complete the construction of the simulation system. This eliminates the need to manually create devices and configure data links one by one in the simulation platform, greatly improving construction efficiency.

[0032] 2. Automatic updates of the simulation system are achieved after modifications to the topology diagram. This invention establishes an association index and change detection mechanism between the topology diagram and the simulation system. When the user edits the topology diagram, changes are automatically detected and the simulation system is updated synchronously. This completely solves the problem of inconsistency between the topology diagram and the simulation system, and avoids risks such as simulation verification results deviating from reality, debugging work based on incorrect system structures, and control logic being sent to removed or changed device nodes. This also reduces manual maintenance costs.

[0033] 3. A dedicated configuration construction solution for the HVAC field is provided. The equipment primitives of this invention are directly associated with the object model (including a complete digital definition at the equipment model level), and the algorithm primitives are directly associated with the external algorithm model (including input-output mapping relationships). Compared with general configuration tools, this is more in line with the construction requirements of HVAC digital simulation systems.

[0034] 4. It lowers the technical barrier to building and modifying digital simulation systems. Users do not need to understand the specific structure of the underlying physical model or the implementation details of the algorithm model. They can build and modify the simulation system simply by using graphical drag-and-drop and connection operations, enabling non-technical personnel to participate in the construction of digital simulation systems. 5. The present invention also provides a design platform for building a digital simulation system for HVAC, which uses physical models as a unified data foundation to completely solve the problem of data silos.

[0035] 6. In the design platform for the constructed HVAC digital simulation system, the mechanism algorithms are independently constructed and bound on demand, realizing reusable management of algorithm assets. The design platform automatically generates and uniformly accesses supplementary mechanism points, eliminating the gap between physical and computational data. The design platform unifies input-output mapping relationships, enabling standardized access and pluggable expansion of external algorithm models. Attached Figure Description

[0036] Figure 1 This is a schematic block diagram of the module structure of a design platform for a digital simulation system for heating, ventilation, and air conditioning used in the execution of the method of the present invention. Detailed Implementation

[0037] The present invention will now be described in further detail with reference to specific embodiments and accompanying drawings.

[0038] Optimal implementation method: A method for automatically generating a digital simulation system for HVAC based on topology synchronization includes the following steps: S1 first completes the drawing of the current HVAC configuration topology in the topology drawing window, and then builds the corresponding digital simulation system based on the current HVAC configuration topology, forming a historical record; Also includes: S2 monitors the editing and saving operations of the topology drawing window in real time. When an editing and saving action is detected in the topology drawing window, a synchronous detection process is executed. The synchronous detection process includes: comparing the current structured data of the topology with the structured data of the topology recorded when the simulation system was built most recently, and identifying the changed content. The comparison uses the following matching rules: A unique identifier is pre-assigned to all different elements in the topology diagram. The unique identifier of the configured topology diagram element is used as the primary matching key. If an element identifier exists in both the current topology diagram and the historical record, and the associated object model / algorithm model identifier is consistent, it is determined to be "unchanged". If an element identifier exists in both the current topology diagram and the historical record, but the associated model identifier is inconsistent, it is determined to be "attribute changed", and all elements with changed attributes are added to the change item list. If an element identifier exists in the current topology diagram but not in the historical record, it is determined to be "added", and all newly added elements are added to the new item list. If an element identifier exists in the historical record but not in the current topology diagram, it is determined to be "deleted", and all deleted elements are added to the deletion item list. If the start or end point of a connection relationship changes, it is determined to be "connection changed", and all elements belonging to the connection change are added to the connection change item list. S3 generates a change list based on the comparison results. The change list includes the list of new items, the list of deleted items, the list of changed items, and the list of connection change items. S4 automatically performs follow-up updates to the digital simulation system based on the change list: For the operation of the new item list: based on the object model or algorithm model associated with the new graphic element, create the corresponding device instance or algorithm instance in the digital simulation system, and establish the corresponding data link according to the connection relationship in the topology diagram; For the deletion list operation: based on the association index between the deleted graphic element and the simulation system element, delete the corresponding device instance or algorithm instance and its related data link in the digital simulation system; For the change item list operation: based on the object model or algorithm model after the element replacement, update the definition of the corresponding device instance or algorithm instance in the digital simulation system; For operations on the connection change list: based on the changes in the connection relationships of elements in the topology diagram, add, delete, or modify the corresponding data links in the digital simulation system; After the S5 update is complete, it saves the current topology diagram and the corresponding updated digital simulation system as a new history. It also updates the association index between the configuration topology diagram and the digital simulation system to ensure they remain consistent, and further writes the update results to the synchronization log. Furthermore, if anomalies occur during synchronization (such as missing object models, algorithm incompatibility, data link conflicts, etc.), the system records the anomaly information and marks the corresponding changes for subsequent user verification and processing.

[0039] In this way, this method enables the design platform to automatically detect changes and execute the simulation system to update accordingly when the user adjusts or modifies the topology diagram. This ensures that the topology diagram and the simulation system are always consistent, thus avoiding defects such as deviations between the simulation system and the actual layout, loss of reference value of simulation verification results, and control logic being sent to the wrong device nodes when the topology diagram has been adjusted or modified during the assembly and adjustment of the HVAC system.

[0040] The process of drawing the current HVAC configuration topology diagram in step S1 includes the following steps: S1.1 Drag and drop the equipment elements required for the current design of the HVAC system from the equipment element library to the drawing canvas to generate the corresponding equipment element nodes. Each equipment element node is automatically associated with the corresponding object model. S1.2 Drag and drop the required external algorithm primitives from the algorithm primitive library onto the drawing canvas to generate corresponding algorithm primitive nodes. Each algorithm primitive node is automatically associated with the corresponding external algorithm model. S1.3 Draw connecting lines between device element nodes and algorithm element nodes using a connecting tool to establish data flow relationships. The data flow relationships specifically include: the data source relationship between device element output points and algorithm element input ports, and the data target relationship between algorithm element output ports and device element input points. After completing all drags and drops and connections in S1.4, the current HVAC configuration topology diagram is completed. The configuration topology diagram automatically records the corresponding structured data, including the equipment element list (the object model identifier associated with each element), the algorithm element list (the algorithm model identifier associated with each element), and the connection relationship list (the start and end identifiers of each connection line).

[0041] This method uses a graphical drag-and-drop interface and connecting lines to represent the equipment composition, algorithm configuration, and data flow relationships of an HVAC system. This graphical representation is then automatically converted into structured data, achieving a transformation from a "user-operable graphical interface" to "computer-parsable structured data." Users do not need to manually write any configuration files or code; they can simply use intuitive drag-and-drop operations to digitally define the topology of the HVAC system. This definition is accurately recorded by the system in a structured form, providing a complete data foundation for the system to automatically call the object model and algorithm model to complete the simulation system construction in subsequent steps. This effectively avoids errors and omissions caused by manual configuration and lowers the technical threshold for building digital simulation systems.

[0042] In implementation, the construction of the corresponding digital simulation system based on the current HVAC configuration topology diagram in step S1 includes the following sub-steps: S1.5 sends a command to the design platform to build a digital simulation system by using the "Build Simulation System" button (or a similar triggering method) in the drawing window; The S1.6 design platform responds to the command by reading the structured data of the current configuration topology diagram, retrieving the corresponding object models from the object model library one by one according to the device element list, and creating the device instance corresponding to the digital simulation system; retrieving the corresponding algorithm model from the algorithm repository one by one according to the algorithm element list, and creating the corresponding algorithm instance in the digital simulation system; and establishing the data link between the device instance and the algorithm instance according to the connection relationship list to form the corresponding digital simulation system. The S1.7 design platform archives the completed digital simulation system as a project file, which contains structured data including a list of device instances, a list of algorithm instances, data link configurations, and a topology diagram.

[0043] This method achieves automatic mapping from structured data in the configuration topology diagram to a runnable simulation system: the system parses the structured data and retrieves the corresponding complete object model definition from the object model library based on the object model identifier in the device primitive list, creating the corresponding device instance in the simulation runtime space; it retrieves the corresponding algorithm definition from the algorithm repository based on the algorithm model identifier in the algorithm primitive list, creating the corresponding algorithm instance; and it establishes the data link between the device instance and the algorithm instance based on the start and end identifiers recorded in the connection relationship list. After the user completes the topology diagram drawing, a single click is all it takes for the system to automatically create all device instances, algorithm instances, and data links in the simulation system, eliminating the need for manual configuration by the user. This achieves one-click rapid construction from "graphical design" to "runnable simulation system," significantly improving the construction efficiency of digital simulation systems.

[0044] In implementation, S1 further includes: The S1.8 design platform establishes an association index between the configuration topology diagram and the digital simulation system, binding the unique identifier of each element in the topology diagram with the identifier of the corresponding device instance / algorithm instance in the simulation system, so that there is a one-to-one mapping relationship between the elements of the topology diagram and the elements of the simulation system.

[0045] Thus, this method, based on the completion of the simulation system construction, further establishes a one-to-one mapping relationship between configuration topology diagram elements and simulation system elements. The specific function of this association index is: when the user subsequently edits or modifies the topology diagram, the system can quickly locate the corresponding device instance or algorithm instance in the simulation system through the unique identifier of the element, thereby accurately performing subsequent follow-up update operations and ensuring that the topology diagram and the simulation system always remain consistent. This association index provides data support for the bidirectional mapping between the topology diagram and the simulation system, and is the technical guarantee for the subsequent automatic synchronization update mechanism.

[0046] In implementation, this method is based on a design platform built using a digital simulation system for HVAC systems. (See [link to relevant documentation]). Figure 1 As shown, the design platform includes a digital simulation system framework building module (used to draw the configuration topology diagram, establish the mapping relationship between the external algorithm model and the object model points, and generate a digital simulation system framework based on the configuration topology diagram), an object model instantiation module (to realize the initial construction of the digital simulation system and complete the instantiation), and a digital simulation system instance update module (to realize the follow-up update of the digital simulation system). The digital simulation system framework building module has a topology drawing window, which includes a device drag-and-drop sub-window connected to the object model library, an algorithm drag-and-drop sub-window connected to the algorithm repository, a data connection drawing sub-window, and an execution order configuration sub-window. The device drag-and-drop sub-window is used to display a list of all available object models in the object model library, and to receive user drag-and-drop operations to generate corresponding device elements on the construction canvas (the construction canvas refers to the main interface of the topology drawing window). Each device element carries a complete list of points of the corresponding object model. The algorithm drag-and-drop sub-window is used to display a list of all available external algorithm models in the algorithm repository, and to receive user drag-and-drop operations to generate corresponding algorithm primitives on the construction canvas. Each algorithm primitive carries a corresponding input-output mapping relationship. The data connection drawing sub-window is used to receive the user's connection operation between the device graphic elements and the algorithm graphic elements to complete the drawing of the configuration topology diagram (i.e. to realize the graphical construction of the digital simulation system framework), establish the data source relationship between the output point of the object model and the input port of the external algorithm model, as well as the data target relationship between the output port of the external algorithm model and the input point of the object model, and record the start point and end point of each connection to form a data mapping relationship list. The execution order configuration sub-window is used to receive the user's execution priority settings for each algorithm primitive and form an execution order list; The digital simulation system framework building module also has a structured data export unit connected to the topology drawing window, which is used to read the list of all device primitives, algorithm primitives, data mapping relationship list and execution order list on the building canvas, and serialize them into JSON or XML format structured framework data, which serves as the configuration basis for subsequent steps. The object model instantiation module has a structure framework import window, a device instantiation window, and a data link establishment window. The structural framework import window is used to connect with the structured data export unit of the digital simulation system framework building module, receive and parse the structural framework data, extract the device list, algorithm list, data mapping relationship list and execution order list, and parse it into system instantiation configuration data. The device instantiation window is connected to the structural framework import window. It is used to establish a connection with the object model library one by one according to the parsed device list, read the object model definition corresponding to each device, create the corresponding device instance object in the system, and assign a unique instance identifier to each device instance. Furthermore, the device instantiation window is also used to initialize all points (including input points, output points, and mechanism supplement points) of each device instance in the runtime data space, so that the device instance enters the "runnable device object" state from the "object model definition" state. The data link establishment window is connected to the device instantiation window and is used to establish the following data links one by one according to the parsed data mapping relationship list: establishing a data acquisition mapping between the input points of each device instance and the corresponding physical sensor data source; establishing a control mapping between the output points of each device instance (including the native output points of the object model and the mechanism supplementary points) and the corresponding physical actuator control address; associating the input port of the algorithm instance with its data source point; and associating the output port of the algorithm instance with its data target point. This completes the construction of the required digital simulation system and saves its topology structured data to a connected historical record management unit. Furthermore, the data link establishment window is also used to read and apply the execution order list, write the execution priority of each algorithm instance into the scheduler's configuration, and enter the running phase.

[0047] The digital simulation system instance update module includes a topology change monitoring unit, a change detection and comparison unit, and a follow-up update execution unit.

[0048] The topology change monitoring unit is connected to the topology drawing window and is used to monitor in real time the editing and modification operations performed by the user on the saved configuration topology in the topology drawing window. The editing and modification operations include, but are not limited to: adding device elements, deleting device elements, modifying device element attributes (including changing associated object models), adding algorithm elements, deleting algorithm elements, and modifying connection relationships. Whenever the user completes an editing action, the topology change monitoring unit automatically triggers the change detection and comparison unit to start.

[0049] The change detection and comparison unit is connected to the topology change monitoring unit, the topology drawing window, and the history management unit, respectively. Upon receiving a trigger signal from the topology change monitoring unit, it reads the structured data of the current topology from the topology drawing window and compares it with the structured data of the historical topology saved during the most recent construction of the digital simulation system, read from the history management unit, to identify changes. The comparison uses the unique identifier of the element as the primary matching key and is determined according to the following rules: if the element identifier exists in both the current topology and the history, and the associated object model or algorithm model identifier is consistent, it is determined as "no change"; if the element identifier exists but the associated model identifier is inconsistent, it is determined as "attribute change"; if the element identifier exists in the current topology but not in the history, it is determined as "added"; if the element identifier exists in the history but not in the current topology, it is determined as "deleted"; if the start or end identifier of a connection relationship changes, it is determined as "connection change". The change detection and comparison unit generates a change list based on the determination results, which includes a list of added items, a list of deleted items, a list of attribute change items, and a list of connection change items.

[0050] The follow-up update execution unit is connected to the change detection and comparison unit and is used to automatically execute follow-up update operations of the digital simulation system according to the change list. Its specific execution logic is as follows: For "Added" items in the change list, based on the object model or algorithm model identifier associated with the newly added graphic element, the corresponding definition is retrieved from the object model library or algorithm repository, and a corresponding device instance or algorithm instance is created in the simulation system. A corresponding data link is established based on the connection relationship in the topology diagram. For "Deleted" items, based on the association index between the deleted graphic element and simulation system elements, the corresponding device instance or algorithm instance and its associated data link are deleted in the simulation system. For "Attribute Change" items, based on the object model or algorithm model identifier after the graphic element is replaced, the definition of the corresponding device instance or algorithm instance is updated in the simulation system. For "Connection Change" items, based on the changes in the connection relationship in the topology diagram, the corresponding data link is added, deleted, or modified in the simulation system. If the follow-up update execution unit encounters an anomaly (including missing object models, algorithm incompatibility, or data link conflicts) during the update operation, it records the anomaly information and skips the change item, continuing to execute subsequent change items.

[0051] The historical record management unit is also connected to the follow-up update execution unit. After the follow-up update execution unit completes its update operation, it saves the structured data of the current topology diagram and the corresponding digital simulation system configuration as a new historical record, and updates the association index between the configured topology diagram and the digital simulation system, ensuring that the one-to-one mapping between topology diagram elements and simulation system elements remains up-to-date. Furthermore, the historical record management unit is also used to store synchronization logs, which include timestamps of each synchronization operation, change list content, follow-up update execution results, and exception information.

[0052] This design allows the platform to automatically detect the topology drawing status and automatically update and generate a new HVAC digital simulation system. This ensures that the current simulation system is consistent with the design changes and avoids defects such as forgetting to update the simulation system after design changes during the assembly and adjustment of the HVAC system, which can lead to deviations between the simulation system and the actual layout, loss of reference value of simulation verification results, and control logic being sent to the wrong equipment nodes.

[0053] The design platform also includes a physical model building module, a physical model library, an algorithm building module, an algorithm repository, and a mechanism algorithm binding module. The object model building module is used to create, edit, and store object models; the object model library is used to store all the object models that have been built; the algorithm building module is used to create, store, and verify mechanism algorithms and external algorithm models; the algorithm repository is used to store all the mechanism algorithms and external algorithm models that have been built; and the mechanism algorithm binding module is used to bind object models and mechanism algorithms, configure scene matching rules, and verify binding relationships. Specifically, the structure of each module is as follows: (a) Object Model Construction Module The object model building module provides an object model editor with an editing input window, allowing users to interactively complete the following data input operations: filling in equipment metadata information (including brand, model, equipment type, and version); adding equipment input point definition information, including point name, data type, numerical range (minimum / maximum value), unit, and description; adding equipment output point information, including point name, data type, numerical range (minimum / maximum value), unit, and description; and adding equipment design parameter information, including rated power, rated flow rate, design temperature, and design pressure. After the data output operation is completed, the object model building module serializes the object model data in JSON or XML format and stores it in the object model library.

[0054] (ii) Object Model Library The object model library is implemented using a relational database or a document-oriented database to store all constructed object models. The storage structure of each object model includes: a unique model identifier, equipment metadata (brand, model, equipment type, version), a list of input points (each point includes name, data type, minimum value, maximum value, unit, and description), a list of output points (each point includes name, data type, minimum value, maximum value, unit, and description), a list of design parameters (parameter name, value, and unit), creation time, modification time, and version number. The object model library has a search window associated with each stored object model (for searching and retrieving object models) and a add / delete / modify window (for modifying object model data).

[0055] (III) Algorithm Construction Module The algorithm construction module includes an algorithm editor that allows users to programmatically construct physical mechanism algorithms. The algorithm editor has an algorithm code input window, which embeds a preset algorithm template that the user's input algorithm code must follow. The algorithm template defines the declaration format of the algorithm's input parameters, output parameters, and adjustable parameters. The algorithm construction module also has a syntax checking unit connected to the algorithm code input window. This unit performs syntax checks on the input code and verifies the algorithm code by calling a compiler or interpreter, checking whether the input and output parameters are completely declared and identifying missing or redundant definitions. The algorithm construction module also has an algorithm verification unit connected to the syntax checking unit. After the syntax check passes, the verification unit calls a preset standard test dataset to test and verify the algorithm, comparing the algorithm's calculation results with preset standard values. If the deviation is within the allowable range, the verification is marked as successful. The verification unit also has an output terminal connected to an algorithm repository, used to store verified algorithms in the algorithm repository, with the status marked as "verified."

[0056] The algorithm building module also supports the storage of physical mechanism calculation code and external algorithm models required for control, implemented in programming languages ​​(including but not limited to Python, C++, and Java).

[0057] (iv) Algorithm repository The algorithm repository employs the same data storage technology as the object model library, serving as a database for storing all constructed mechanistic algorithms and external algorithm models. The algorithm repository includes an algorithm storage unit connected to the output of the algorithm construction module, used to receive algorithm data, index it according to algorithm type and applicable device type, and then store it in the database. The algorithm repository also includes a search operation window connected to the algorithm storage unit, used to receive user search commands, perform searches by name, version, device type, and algorithm type, and display the results. Furthermore, it may include a version management unit connected to the algorithm storage unit, used to save historical versions of each algorithm record and support version rollback.

[0058] (v) Mechanism Algorithm Binding Module The mechanism algorithm binding module has an algorithm binding configuration window, which includes a physical model point display sub-window and an available algorithm display sub-window. The physical model point display sub-window is used to establish a connection with the physical model library, read and display the complete point list of the currently selected physical model. The available algorithm display sub-window is used to establish a connection with the algorithm repository, display the list of available mechanism algorithms with the status "verified" in the algorithm repository, and receive the user's binding selection command to establish an association record between the algorithm and the physical model. The mechanism algorithm binding module also has an automatic mapping relationship generation unit connected to the algorithm binding configuration window, which is used to automatically generate input parameters based on the algorithm's input parameter list and the physical model's input point list after the user completes the algorithm selection. The system includes a mapping relationship table and an output parameter mapping relationship table automatically generated based on the algorithm's output parameter list and the object model's output point list. The mechanism algorithm binding module also has a mechanism supplementary point creation unit connected to the automatic mapping relationship generation unit. This unit automatically creates mechanism supplementary point definitions in the object model's output points after the output mapping relationship table is generated, and records their associated algorithm identifiers and mapping relationships. The mechanism algorithm binding module also includes a scene matching rule configuration window, which receives the corresponding mechanism algorithms specified by the user for different running scenarios and stores the matching conditions in the form of a rule table. Finally, it includes a binding relationship verification unit connected to the mechanism supplementary point creation unit, which simulates algorithm calls using preset test data after binding is completed to confirm that the data can flow correctly.

[0059] Therefore, the aforementioned platform can be used to quickly and efficiently generate a digital simulation system for HVAC systems. This generated system can simulate and reproduce the actual working scenarios of HVAC systems in real time, and can automatically run internal system mechanism algorithms and external control algorithms, greatly improving the system's automatic control effect. Furthermore, the generated digital simulation system can automatically update along with the topology diagram during the adjustment of air conditioning system components. This avoids the tedious work of manually modifying each device instance, data link, and algorithm configuration in the simulation system during component adjustments, as well as the inconsistency between the simulation system and the actual system structure caused by untimely manual modifications or operational errors, ensuring that the simulation system always remains synchronized with the actual design.

Claims

1. A method for automatically generating a digital simulation system for HVAC based on topology synchronization, comprising the following steps: S1 first completes the drawing of the current HVAC configuration topology in the topology drawing window, and then builds the corresponding digital simulation system based on the current HVAC configuration topology, forming a historical record; Its characteristic is that it further includes: S2 monitors the editing and saving operations of the topology drawing window in real time. When an editing and saving action is detected in the topology drawing window, a synchronous detection process is executed. The synchronous detection process includes: comparing the current structured data of the topology with the structured data of the topology recorded when the simulation system was built most recently, and identifying the changed content. S3 generates a change list based on the comparison results. The change list includes the list of new items, the list of deleted items, the list of changed items, and the list of connection change items. S4 automatically performs follow-up updates to the digital simulation system based on the change list: For the operation of the new item list: based on the object model or algorithm model associated with the new graphic element, create the corresponding device instance or algorithm instance in the digital simulation system, and establish the corresponding data link according to the connection relationship in the topology diagram; For the deletion list operation: based on the association index between the deleted graphic element and the simulation system element, delete the corresponding device instance or algorithm instance and its related data link in the digital simulation system; For the change item list operation: based on the object model or algorithm model after the element replacement, update the definition of the corresponding device instance or algorithm instance in the digital simulation system; For operations on the connection change list: based on the changes in the connection relationships of elements in the topology diagram, add, delete, or modify the corresponding data links in the digital simulation system; After the S5 update is completed, it saves the current topology diagram and the corresponding updated digital simulation system as a new history, and updates the association index between the configuration topology diagram and the digital simulation system to ensure that the two remain consistent.

2. The automatic generation method for a HVAC digital simulation system based on topology synchronization as described in claim 1, characterized in that, The comparison described in S2 uses the following matching rules: A unique identifier is pre-assigned to all different elements in the topology diagram. The unique identifier of the configured topology diagram element is used as the primary matching key. If the element identifier exists in both the current topology diagram and the historical record, and the associated object model / algorithm model identifier is consistent, it is determined as "unchanged". If the element identifier exists in both the current topology diagram and the historical record, but the associated model identifier is inconsistent, it is determined as "attribute changed", and all elements with changed attributes are included in the change item list. If the element identifier exists in the current topology diagram but not in the historical record, it is determined as "added", and all added elements are included in the add item list. If the element identifier exists in the historical record but not in the current topology diagram, it is determined as "deleted", and all deleted elements are included in the delete item list. If the start or end point of the connection relationship changes, it is determined as "connection changed", and all elements belonging to the connection change are included in the connection change item list.

3. The automatic generation method for a HVAC digital simulation system based on topology synchronization as described in claim 1, characterized in that, The steps in S1 to complete the current HVAC configuration topology diagram drawing include the following: S1.1 Drag and drop the equipment elements required for the current design of the HVAC system from the equipment element library to the drawing canvas to generate the corresponding equipment element nodes. Each equipment element node is automatically associated with the corresponding object model. S1.2 Drag and drop the required external algorithm primitives from the algorithm primitive library onto the drawing canvas to generate corresponding algorithm primitive nodes. Each algorithm primitive node is automatically associated with the corresponding external algorithm model. S1.3 Draw connecting lines between device element nodes and algorithm element nodes using a connecting tool to establish data flow relationships. The data flow relationships specifically include: the data source relationship between device element output points and algorithm element input ports, and the data target relationship between algorithm element output ports and device element input points. After completing all drags and drops and connections in S1.4, the current HVAC configuration topology diagram is drawn. The configuration topology diagram automatically records the corresponding structured data, including the equipment element list, algorithm element list, and connection relationship list.

4. The automatic generation method for a HVAC digital simulation system based on topology synchronization as described in claim 1, characterized in that, The construction of the corresponding digital simulation system based on the current HVAC configuration topology diagram in S1 includes the following sub-steps: S1.5 sends a command to the design platform to build a digital simulation system by clicking the "Build Simulation System" button in the drawing window; The S1.6 design platform responds to the command by reading the structured data of the current configuration topology diagram, retrieving the corresponding object models from the object model library one by one according to the device element list, and creating the device instance corresponding to the digital simulation system; retrieving the corresponding algorithm model from the algorithm repository one by one according to the algorithm element list, and creating the corresponding algorithm instance in the digital simulation system; and establishing the data link between the device instance and the algorithm instance according to the connection relationship list to form the corresponding digital simulation system. The S1.7 design platform archives the completed digital simulation system as a project file, which contains structured data including a list of device instances, a list of algorithm instances, data link configurations, and a topology diagram.

5. The automatic generation method for a HVAC digital simulation system based on topology synchronization as described in claim 4, characterized in that, S1 also includes: The S1.8 design platform establishes an association index between the configuration topology diagram and the digital simulation system, binding the unique identifier of each element in the topology diagram with the identifier of the corresponding device instance and algorithm instance in the simulation system, so that there is a one-to-one mapping relationship between the elements of the topology diagram and the elements of the simulation system.

6. The automatic generation method for a HVAC digital simulation system based on topology synchronization as described in claim 1, characterized in that, The method is based on a design platform for building a digital simulation system for HVAC systems. The design platform includes a digital simulation system framework building module, a physical model instantiation module, and a digital simulation system instance updating module. The digital simulation system framework building module has a topology drawing window, which includes a device drag-and-drop sub-window connected to the object model library, an algorithm drag-and-drop sub-window connected to the algorithm repository, a data connection drawing sub-window, and an execution order configuration sub-window. The device drag-and-drop sub-window is used to display a list of all available object models in the object model library, and to receive user drag-and-drop operations to generate corresponding device elements on the construction canvas. Each device element carries a complete list of points of the corresponding object model. The algorithm drag-and-drop sub-window is used to display a list of all available external algorithm models in the algorithm repository, and to receive user drag-and-drop operations to generate corresponding algorithm primitives on the construction canvas. Each algorithm primitive carries a corresponding input-output mapping relationship. The data connection drawing sub-window is used to receive the user's connection operation between device elements and algorithm elements to complete the drawing of the configuration topology diagram, establish the data source relationship between the output point of the object model and the input port of the external algorithm model, as well as the data target relationship between the output port of the external algorithm model and the input point of the object model, and record the start point and end point of each connection to form a data mapping relationship list. The execution order configuration sub-window is used to receive the user's execution priority settings for each algorithm primitive and form an execution order list; The digital simulation system framework building module also has a structured data export unit connected to the topology drawing window, which is used to read the list of all device primitives, algorithm primitives, data mapping relationship list and execution order list on the building canvas, and serialize them into JSON or XML format structured framework data, which serves as the configuration basis for subsequent steps. The object model instantiation module has a structure framework import window, a device instantiation window, and a data link establishment window. The structural framework import window is used to connect with the structured data export unit of the digital simulation system framework building module, receive and parse the structural framework data, extract the device list, algorithm list, data mapping relationship list and execution order list, and parse it into system instantiation configuration data. The device instantiation window is connected to the structure framework import window. It is used to establish a connection with the object model library one by one according to the parsed device list, read the object model definition corresponding to each device, create the corresponding device instance object in the system, and assign a unique instance identifier to each device instance. The data link establishment window is connected to the device instantiation window and is used to establish the following data links one by one according to the parsed data mapping relationship list: establish a data acquisition mapping between the input point of each device instance and the corresponding physical sensor data source; establish a control mapping between the output point of each device instance and the corresponding physical actuator control address; associate the input port of the algorithm instance with its data source point; associate the output port of the algorithm instance with its data target point; construct the required digital simulation system and save its topology structured data to a connected historical record management unit. The digital simulation system instance update module includes a topology map change monitoring unit, a change detection and comparison unit, and a follow-up update execution unit. The topology change monitoring unit is connected to the topology drawing window and is used to monitor in real time the editing and modification operations performed by the user on the saved configuration topology in the topology drawing window. The editing and modification operations include, but are not limited to: adding device elements, deleting device elements, modifying device element attributes, adding algorithm elements, deleting algorithm elements, and modifying connection relationships. Whenever the user completes an editing action, the topology change monitoring unit automatically triggers the change detection and comparison unit to start. The change detection and comparison unit is connected to the topology change monitoring unit, the topology drawing window, and the history management unit, respectively. Upon receiving a trigger signal from the topology change monitoring unit, it reads the structured data of the current topology from the topology drawing window and compares it with the structured data of the historical topology saved during the most recent construction of the digital simulation system, read from the history management unit, to identify changes. The comparison uses the unique identifier of the element as the primary matching key and is determined according to the following rules: if the element identifier exists in both the current topology and the history, and the associated object model or algorithm model identifier is consistent, it is determined as "no change"; if the element identifier exists but the associated model identifier is inconsistent, it is determined as "attribute change"; if the element identifier exists in the current topology but not in the history, it is determined as "added"; if the element identifier exists in the history but not in the current topology, it is determined as "deleted"; if the start or end identifier of the connection relationship changes, it is determined as "connection change". The change detection and comparison unit generates a change list based on the determination results, which includes a list of added items, a list of deleted items, a list of attribute change items, and a list of connection change items. The follow-up update execution unit is connected to the change detection and comparison unit, and is used to automatically execute the follow-up update operation of the digital simulation system according to the change list. Its specific execution logic is as follows: For the "Add" item in the change list, according to the object model or algorithm model identifier associated with the added graphic element, the corresponding definition is retrieved from the object model library or algorithm repository, the corresponding device instance or algorithm instance is created in the simulation system, and the corresponding data link is established according to the connection relationship in the topology diagram; For the "Delete" item, according to the association index between the deleted graphic element and the simulation system element, the corresponding device instance or algorithm instance and its associated data link are deleted in the simulation system; For the "Attribute Change" item, according to the object model or algorithm model identifier after the graphic element is replaced, the definition of the corresponding device instance or algorithm instance is updated in the simulation system; For the "Connection Change" item, according to the change in the connection relationship in the topology diagram, the corresponding data link is added, deleted, or modified in the simulation system; The historical record management unit is also connected to the follow-up update execution unit. After the follow-up update execution unit completes the update operation, it saves the structured data of the current topology diagram and the corresponding digital simulation system configuration as a new historical record, and updates the association index between the configuration topology diagram and the digital simulation system to ensure that the one-to-one mapping relationship between topology diagram elements and simulation system elements is always up-to-date.

7. The automatic generation method for a HVAC digital simulation system based on topology synchronization as described in claim 6, characterized in that, The device instantiation window is also used to initialize all points of each device instance in the runtime data space, so that the device instance can enter the runnable device object state from the object model definition state.

8. The automatic generation method for a HVAC digital simulation system based on topology synchronization as described in claim 6, characterized in that, The historical record management unit is also used to store synchronization logs, which include timestamps for each synchronization operation, change list content, follow-up update execution results, and exception information.

9. The automatic generation method for a HVAC digital simulation system based on topology synchronization as described in claim 6, characterized in that, The design platform also includes a physical model building module, a physical model library, an algorithm building module, an algorithm repository, and a mechanism algorithm binding module; The object model building module is used to create, edit, and store object models; the object model library is used to store all the object models that have been built; the algorithm building module is used to create, store, and verify mechanism algorithms and external algorithm models; the algorithm repository is used to store all the mechanism algorithms and external algorithm models that have been built; and the mechanism algorithm binding module is used to bind object models and mechanism algorithms, configure scene matching rules, and verify binding relationships.

10. The automatic generation method for a HVAC digital simulation system based on topology synchronization as described in claim 9, characterized in that, The object model construction module provides an object model editor with an editing input window, which allows users to interactively complete the following data input operations: fill in device metadata information; add device input point definition information, including point name, data type, numerical range, unit and description; add device output point information, including point name, data type, numerical range, unit and description. Add equipment design parameter information, including rated power, rated flow rate, design temperature, and design pressure; After the data output operation is completed, the object model construction module serializes the object model data in JSON or XML format and stores it in the object model library; The object model library is implemented using a relational database or a document database and is used to store all constructed object models. The storage structure of each object model includes: a unique model identifier, equipment metadata, a list of input points, a list of output points, a list of design parameters, creation time, modification time, and version number. The object model library has a search window and an add, delete, and modify window associated with each stored object model. The algorithm construction module includes an algorithm editor that allows users to programmatically construct physical mechanism algorithms. The algorithm editor has an algorithm code input window with a pre-defined algorithm template that the user's input code must follow. This template defines the declaration format for algorithm input parameters, output parameters, and adjustable parameters. The algorithm construction module also includes a syntax checking unit connected to the algorithm code input window. This unit performs syntax checks on the input code and verifies it by calling a compiler or interpreter, checking for complete declarations of input and output parameters and identifying missing or redundant definitions. Furthermore, the algorithm construction module includes an algorithm verification unit connected to the syntax checking unit. After passing the syntax check, this unit calls a pre-defined standard test dataset to test and verify the algorithm, comparing the algorithm's calculation results with pre-defined standard values. If the deviation is within the allowable range, the algorithm is marked as verified. The verification unit also has an output terminal connected to an algorithm repository, used to store verified algorithms in the repository, with the status marked as "verified." The algorithm repository is implemented using the same data storage technology as the object model library, and is a database used to store all constructed mechanistic algorithms and external algorithm models. The algorithm repository has an algorithm storage unit connected to the output end of the algorithm construction module, which is used to receive algorithm data and store it in the database after indexing by algorithm type and applicable device type. The algorithm repository also has a search operation window connected to the algorithm storage unit, which is used to receive user search instructions, search by name, version, device type, and algorithm type, and display the results. It also includes a version management unit connected to the algorithm storage unit, which is used to save historical versions of each algorithm record and support version rollback. The mechanism algorithm binding module has an algorithm binding configuration window, which includes a sub-window displaying object model points and a sub-window displaying available algorithms. The object model point display sub-window is used to establish a connection with the object model library, read and display the complete point list of the currently selected object model. The available algorithm display sub-window is used to establish a connection with the algorithm repository, display the list of available mechanism algorithms with the status "verified" in the algorithm repository, and receive the user's binding selection command to establish an association record between the algorithm and the object model. The mechanism algorithm binding module also has an automatic mapping relationship generation unit connected to the algorithm binding configuration window, which is used to automatically generate input parameters based on the algorithm's input parameter list and the object model's input point list after the user completes the algorithm selection. The system includes a mapping relationship table and an output parameter mapping relationship table automatically generated based on the algorithm's output parameter list and the object model's output point list. The mechanism algorithm binding module also has a mechanism supplementary point creation unit connected to the automatic mapping relationship generation unit. This unit automatically creates mechanism supplementary point definitions in the object model's output points after the output mapping relationship table is generated, and records their associated algorithm identifiers and mapping relationships. The mechanism algorithm binding module also includes a scene matching rule configuration window, which receives the corresponding mechanism algorithms specified by the user for different running scenarios and stores the matching conditions in the form of a rule table. Finally, it includes a binding relationship verification unit connected to the mechanism supplementary point creation unit, which simulates algorithm calls using preset test data after binding is completed to confirm that the data can flow correctly.

Images