A power equipment failure simulation analysis modeling system

Abstract

This invention belongs to the field of simulation modeling technology, and particularly relates to a power equipment fault simulation analysis modeling system. It includes at least an interaction layer, a logic processing layer, and a data management layer. The interaction layer includes model editing interaction components, simulation interaction components, and interaction control components. The logic processing layer includes modeling processing components, simulation parameter editing components, and import / export components. The data management layer includes a power equipment model database and a power equipment fault database. This application is intended for power equipment simulation teaching, fault analysis, and other purposes, meeting the application needs of teaching, experimentation, verification analysis, and other fields. Its main purpose is to provide a solution based on current simulation platforms that better achieves compatibility with various 3D simulation modeling software and simulation analysis data platforms, simplifies the power equipment fault simulation system, and enables better application in teaching analysis.

Description

Technical Field

[0001] This invention belongs to the field of simulation modeling technology, and in particular relates to a power equipment fault simulation analysis modeling system. Background Technology

[0002] Power equipment is the core of various equipment and instrument systems. Its normal operation is essential for ensuring the basic functions of these systems. Fault analysis and handling of power equipment constitute a significant portion of the work involved in the use and maintenance of critical equipment. Power equipment has a complex overall structure, involving mechanical, electrical, and energy systems, making it a key and challenging topic in related training. Compared to other small and medium-sized mechanical structures or components, power equipment has more parts, more complex interactions, and is typically used in a relatively isolated and closed environment. In daily learning, there is a lack of intuitive methods for observation and analysis. Therefore, simulation technology has become a new approach for learning the principles and structure of large and complex equipment and teaching fault analysis and handling. Simulation systems can simplify equipment structure and working principles, improving learners' efficiency in understanding and analyzing complex equipment. It is an effective auxiliary teaching method before practical operation. However, current simulation analysis of power equipment is mainly based on dynamic models for theoretical verification simulations, which cannot meet the needs of actual equipment teaching and analysis. Summary of the Invention

[0003] The purpose of this invention is to provide a system for simulating power equipment faults, primarily used in teaching, experimental analysis, and other applications, based on practical needs.

[0004] To achieve the above objectives, the present invention adopts the following technical solution.

[0005] A power equipment fault simulation analysis and modeling system includes at least an interaction layer, a logic processing layer, and a data management layer.

[0006] The interaction layer includes model editing interaction components, simulation interaction components, and interaction control components;

[0007] The model editing interactive component is used to retrieve the 3D model simulation data generated by the modeling processing component, and to generate power equipment simulation relationship data based on the simulation topology connection relationship of the 3D model generated by the simulation parameter editing component.

[0008] The simulation interaction component is used to retrieve the simulation information stored in the power equipment model database and equipment simulation template library in the data management layer based on the 3D model simulation relationship data generated by the model editing interaction component, and generate corresponding simulation expression data.

[0009] Interactive control components are used to establish interface controls and mapping tables between interface controls and specific functions and interactive actions using visual and graphical controls.

[0010] The logic processing layer includes modeling processing components, simulation parameter editing components, and import / export components;

[0011] The modeling processing component is used to read the interactive operation content obtained by the interactive control component and perform logical operation processing on the simulation model according to the interactive operation category.

[0012] The simulation parameter editing component is used to read the interactive operation commands obtained by the interactive control component, decode the simulation model operation content corresponding to the interactive control commands, and traverse and extract the simulation entity objects and simulation operation content in the operation content through nested loop retrieval. It retrieves three-dimensional model data units of different formats from the power equipment model database and extracts the simulation parameters in the three-dimensional model; it retrieves three-dimensional graphic data of different formats, extracts the geometric and material property information corresponding to the three-dimensional model units, and establishes the mapping relationship between three-dimensional model units, property information, and simulation entities.

[0013] Import / export components are used to establish standardized simulation models, simulation parameter data extraction and storage mechanisms that automatically match the required format, and to configure file classes for input and output data in the corresponding formats; including simulation model output files and system simulation configuration files;

[0014] The simulation model output file is used to save the output signals, output list, and output data; the system simulation configuration file is used to configure the system simulation settings parameters, including the system simulation model decoder and encoder configuration, simulation parameter solver type, and model simulation control parameters.

[0015] The data management layer includes a power equipment model database and a power equipment fault database;

[0016] The power equipment model database is used to define power equipment component models, model topology relationships, model forces, and model force element attributes.

[0017] The power equipment fault database is established using a relational database to create a fault management database, a rule condition database, a rule result database, a fault instance database, and a code database.

[0018] In a further improvement or preferred embodiment of the aforementioned power equipment fault simulation analysis and modeling system, the fault management library is used to store basic fault content codes, fault flag codes, and auxiliary explanation codes.

[0019] The rule condition library is used to store data codes and their encodings related to fault conditions, fault results, and fault simulation methods; the data codes and their encodings are stored in the form of numbers and text characters;

[0020] The rule judgment library is used to store the rules that lead to different fault results under different fault conditions. The fault condition codes in the rule condition library are combined with logical operators to generate judgment rules for different fault results and establish the identification codes for different judgment rules.

[0021] The fault instance library is established based on the fault content, judgment rules, and corresponding fault instances in the aforementioned sub-databases, and also saves data such as the corresponding fault troubleshooting methods.

[0022] The code repository is used to store and manage various relational functions and rule definition functions required for content editing and data processing in each sub-database.

[0023] A further improvement or preferred implementation of the aforementioned power equipment fault simulation analysis and modeling system includes a logic processing layer for data extraction and data transmission processes, specifically comprising:

[0024] a1. The steps of source data acquisition refer to setting at least one neutral format file, and based on targeted data extraction, performing preliminary standardization and classification of simulation model data files that may be involved in the simulation modeling process, so as to facilitate the execution of a relatively unified data extraction process.

[0025] a2. Simulation model data extraction: Parse the simulation model data in the neutral format file, and use the built-in query function of the system platform to extract the required model parameters from the simulation model data.

[0026] a3. The generalized expression of model parameters refers to unifying the units, symbols, and expressions of various model parameters through function transformation and storing them in the generalized expression database of models.

[0027] a4. Model parameter extraction refers to extracting the required model parameter data from the general model database as needed by defining assignment functions and extraction functions, and configuring a neutral model parameter table that matches the aforementioned neutral format file.

[0028] a5. Model simulation association refers to parsing the model parameter table, generating model parameters for simulation, and passing them to the modeling processing component.

[0029] A further improvement or preferred implementation of the aforementioned power equipment fault simulation analysis modeling system is to establish a neutral format based on a line command file with standardized descriptive syntax rules, wherein each line command represents the interactive operation content of a model entity.

[0030] The specification describes the syntax rules consisting of object text representing model entities, action text representing interaction operation categories, and parameter text representing specific attribute values ​​of interaction operations. The object text consists of several model entity IDs or codes, the action text consists of several operation names, and the parameter text consists of operation parameters that match each operation type. Dedicated line continuation characters are configured to determine the content boundaries of each command line, and comment characters are configured to distinguish between command lines and non-command lines.

[0031] The neutral format file uses predefined fixed tag elements in the text document to save simulation model parameter data. The predefined tag elements in the text document include at least:

[0032] Version and encoding tags: These are used to declare the document version and encoding type tags, so as to standardize the definition of subsequent tag elements and functions in the text document. They are usually placed at the very beginning of the text document to determine the standard on which the text document is based at the first time.

[0033] Entity Root Label: Used to define the object that serves as the root simulation entity in the nested relationship of the simulation model. The root simulation entity refers to the object used as the reference for the position and connection relationship of each entity during the model saving process, which is used to quickly locate the reference and realize the location and relationship analysis of simulation entity information.

[0034] Sub-entity tag: Used to define the master-slave nesting of the simulation model. The master-slave nesting refers to the relationship between two simulation entities that are at different levels in the nesting relationship of the simulation model expressed based on a tree structure.

[0035] In a further improvement or preferred embodiment of the aforementioned power equipment fault simulation analysis modeling system, the simulation model output file also uses dynamic parameters to enable the editing of elements in the simulation model output file, or establishes a synchronization port to achieve synchronous updates; the dynamic parameters are implemented through several function commands, including at least: search command function, read command function, compare command function, and set command function, and the function commands are created based on text command lines;

[0036] The search command function locates elements in the simulation model output file through traversal search. The read command function reads data from different element types based on the location located by the search command function. The comparison command function analyzes and compares the read data with the updated data. The set command function reads system synchronization commands or preset storage commands to determine whether to update the read data.

[0037] In a further improvement or preferred implementation of the aforementioned power equipment fault simulation analysis modeling system, the output signal refers to the ID, output format, and saving method of the simulation model output signal determined by file parameters or instructions;

[0038] The output list refers to the list of output signal IDs, overload IDs and their overload counts stored in a linked list, which is used to realize the batch import and export of simulation models and improve the efficiency of reading repetitive parts.

[0039] The output file class refers to the model simulation data and its file storage information saved through predefined neutral files. The file storage information includes the actual path of the simulation model output file, the ID of the simulation model output file, and the storage status flag parameter of the simulation model output file. The storage status flag parameter is used to mark the storage update status of the simulation model output file to determine whether to maintain storage space and ensure the effective storage of the simulation model output file.

[0040] A further improvement or preferred implementation of the aforementioned power equipment fault simulation analysis and modeling system includes a power equipment model database used to establish data tables based on four element classes, specifically including:

[0041] Component model category, used to define the interacting model entities, including at least the main component models of the power equipment, the power component assembly space or basic model;

[0042] Topological relationship categories are used to define the connection relationships between model entities, including at least fixed connections, rotational connections, linear motion connections, planar motion connections, and spherical motion connections;

[0043] The model force category is used to define the interaction relationships between model entities, including two-entity interactions and multi-entity interactions;

[0044] Force element attribute categories are used to define the properties of the interaction forces between model entities, including field forces, stress, elastic forces, and deformation forces.

[0045] A further improvement or preferred implementation of the aforementioned power equipment fault simulation analysis modeling system employs generative rules to establish a rule judgment base. The basic rule form within the rule base is as follows: Where A refers to the fault condition in the rule condition library. or combinations thereof In the combination This means simultaneously satisfying, B refers to satisfying one of the following; B refers to the fault result and its combination. It means Credibility.

[0046] 1. A further improvement or preferred implementation of the aforementioned power equipment fault simulation analysis modeling system, in order to establish a comprehensive rule base, also includes a step for extracting and generating rules from the rule base, including...

[0047] b1. Establishing a fault tree for power equipment: Specifically, based on the definition of fault status and fault type of power equipment, establish a fault dataset for power equipment, determine the causes and occurrence paths of various faults, and on the basis of judging the fault path and fault, determine the highest level fault as the top-level fault.

[0048] b2. Based on the requirements of the power equipment fault simulation system, sort out the system fault states, ignore low-probability events with low impact, and determine the fault tree range boundary; complete the accurate definition of all fault conditions, sort out the logical relationships under the fault conditions, and draw a complete fault tree;

[0049] b3. Extract power equipment fault rule conditions based on the hierarchical relationship between fault tree structures and generate a rule base.

[0050] Further improvements or preferred implementations of the aforementioned power equipment fault simulation analysis modeling system include defining attribute variables and attribute functions to enrich the simulation modeling data storage structure. These are used to define and edit relationships and attributes. The attribute variables include: name, mass, inertia, connection relationship container, entity force container, force element container, position container, and direction container. The attribute variables are string data. The attribute functions include: force action function in each direction, torque action function in each direction, relationship writing function, data writing function, and data reading function.

[0051] To improve reading efficiency, a container size variable is configured to update the flag when the data within the container changes. During the data reading process within the container, the container size variable is used to determine whether all attribute variables have been read and processed, thereby simplifying the data processing flow. Attached Figure Description

[0052] Figure 1 This is a functional structure diagram of the power equipment fault simulation analysis and modeling system. Detailed Implementation

[0053] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the invention. Furthermore, the technical features involved in the various embodiments of this invention described below can be combined with each other as long as they do not conflict with each other.

[0054] This application relates to a power equipment fault simulation analysis and modeling system, mainly used for power equipment simulation teaching, fault analysis, and other applications, meeting the needs of teaching, experimentation, verification analysis, and other fields. Its main purpose is to provide a solution based on current simulation platforms that better achieves compatibility with various 3D simulation modeling software and simulation analysis data platforms, and simplifies the power equipment fault simulation system, enabling it to be better applied to teaching analysis.

[0055] like Figure 1 As shown, the power equipment fault simulation analysis modeling system of this application can be divided into an interaction layer, a logic processing layer and a data management layer from a functional perspective.

[0056] The interaction layer is mainly used to complete human-computer interaction and establish a visual operation interface for interactive operations in all directions during the simulation of power equipment faults, simplifying system operation and use to meet the basic needs of teaching and analysis.

[0057] The interaction layer mainly consists of model editing interaction components, simulation interaction components, and interaction control components. The components mentioned in this application refer to independent functional units built based on UI functional units, related functions / function libraries, or predefined classes within the actual application development platform of the system. In the specific analysis process, the basic functions of each component are decomposed and coded according to the platform's data structure and function set. The specific coding and processing methods are usually created in the form agreed upon by the specific platform.

[0058] The model editing interaction component is mainly used to retrieve the 3D model simulation data generated by the modeling processing component, and to generate power equipment simulation relationship data based on the 3D model simulation topology connection relationship generated by the simulation parameter editing component.

[0059] Based on current technology, the editing and interaction of simulation models are mainly achieved by calling various model editing and processing tools supported by the simulation system platform.

[0060] The simulation interaction component is used to retrieve the simulation information stored in the power equipment model database and equipment simulation template library in the data management layer based on the 3D model simulation relationship data generated by the model editing interaction component, generate the corresponding simulation expression data, and output it through the display interface.

[0061] The interactive control component is used to call the system platform's visual development tools, and to use visual and graphical controls to establish interface controls for various specific functions and interactive actions in the process of power equipment fault analysis simulation and simulation modeling, and to establish a mapping table between the interface controls and the specific functions and interactive actions.

[0062] The logic processing layer is mainly used to complete the backend data processing and analysis, and to establish data interaction channels between the current simulation platform environment and various 3D modeling software, simulation data generation platforms and security systems that may be involved in the actual application process. In this application, it mainly involves the processing of parameter data related to the 3D simulation model of power equipment. According to the functional purpose, this layer can be mainly divided into modeling processing components, simulation parameter editing components and import / export components.

[0063] The modeling processing component is used to read the interactive operation content obtained by the interactive control component and perform logical operation processing on the simulation model according to the interactive operation category.

[0064] The simulation parameter editing component is used to read the interactive operation commands obtained by the interactive control component, decode the simulation model operation content corresponding to the interactive control commands, and traverse and extract the simulation entity objects and simulation operation content in the operation content through nested loop retrieval. It retrieves three-dimensional model data units of different formats from the power equipment model database, extracts simulation parameters from the three-dimensional model (including at least model unit attributes, force element distribution parameters, model constraint parameters, model rigid body parameters, and topological connection relationships); it retrieves three-dimensional graphic data of different formats, extracts the geometric and material property information corresponding to the three-dimensional model units, and establishes the mapping relationship between three-dimensional model units, property information, and simulation entities.

[0065] Furthermore, since the expression and storage methods of simulation model parameters differ in different simulation systems, the aforementioned data tables and attribute information are usually stored in data files of various types and structures. To ensure the effective extraction of necessary data information, the logic processing layer, under the premise of its basic functions, needs to establish necessary data extraction and data transfer processes, including:

[0066] 1. The steps of source data acquisition refer to setting at least one neutral format file, and based on targeted data extraction, performing preliminary standardization and classification of simulation model data files that may be involved in the simulation modeling process, so as to facilitate the execution of a relatively unified data extraction process;

[0067] 2. Simulation model data extraction: Parse the simulation model data in the neutral format file, and use the built-in query function of the system platform to extract the required model parameters from the simulation model data.

[0068] 3. The generalized expression of model parameters refers to unifying the units, symbols, and expressions of various model parameters through function transformation and storing them in a generalized model expression database;

[0069] 4. Model parameter extraction refers to extracting the required model parameter data from the general model database as needed by defining assignment functions and extraction functions, and configuring a neutral model parameter table that matches the aforementioned neutral format file.

[0070] 5. Model simulation association refers to parsing the model parameter table, generating model parameters for simulation, and transferring them to the modeling processing component;

[0071] Furthermore, in the aforementioned steps, the neutral format file is essentially a model description file used to collect and standardize model data. To simplify the data structure and improve reading efficiency and versatility, this embodiment uses a line command file with standardized description syntax rules as the basis for establishing the neutral format. Each line command represents the interactive operation content for a model entity. The standardized description syntax rules consist of object text representing the model entity, action text representing the type of interactive operation, and parameter text representing the specific attribute values ​​of the interactive operation. The object text consists of several model entity IDs or codes, the action text consists of several operation names, and the parameter text consists of operation parameters matching each operation type. For ease of processing, dedicated line continuation characters should be configured to determine the content boundaries of each command line, and comment characters should be configured to distinguish between command lines and non-command lines.

[0072] Furthermore, during the model parsing process, it is necessary to determine various parameters by using keywords from the source model file. In order to obtain keywords, this embodiment uses the TStringList string management class to perform operations such as string separation, addition, deletion, and sorting.

[0073] Furthermore, this invention provides a neutral format file based on a text document, and uses predefined fixed tag elements in the text document to save simulation model parameter data. The predefined tag elements in the text document include at least:

[0074] Version and encoding tags: These are used to declare the document version and encoding type tags, so as to standardize the definition of subsequent tag elements and functions in the text document. They are usually placed at the very beginning of the text document to determine the standard on which the text document is based at the first time.

[0075] Entity Root Label: Used to define the object that serves as the root simulation entity in the nested relationship of the simulation model. The root simulation entity refers to the object used as the reference for the position and connection relationship of each entity during the model saving process, which is used to quickly locate the reference and realize the location and relationship analysis of simulation entity information.

[0076] Sub-entity tag: Used to define the master-slave nesting of the simulation model. The master-slave nesting refers to the relationship between two simulation entities that are at different levels in the nesting relationship of the simulation model expressed based on a tree structure.

[0077] The import / export component is used to establish a standardized mechanism for automatically extracting and storing simulation model and simulation parameter data in or matching the required format, and to configure file classes for input and output data in the corresponding format to achieve data transfer of simulation data; the file classes include at least simulation model output files and system simulation configuration files;

[0078] The simulation model output file is used to save the output signals, output list, and output data.

[0079] The output signal refers to the ID, output format, and saving method of the simulation model output signal determined by file parameters or instructions;

[0080] The output list refers to the list of output signal IDs, overload IDs and their overload counts stored in a linked list, which is used to realize the batch import and export of simulation models and improve the efficiency of reading repetitive parts.

[0081] The output file class refers to the model simulation data and its file storage information saved through predefined neutral files. The file storage information includes the actual path of the simulation model output file, the ID of the simulation model output file, and the storage status flag parameter of the simulation model output file. The storage status flag parameter is used to mark the storage update status of the simulation model output file to determine whether to maintain storage space and ensure the effective storage of the simulation model output file.

[0082] Furthermore, to achieve dynamic processing and ensure that simulation model files at different stages of import and export can achieve unified updates of simulation parameters and states, the simulation model output file also uses dynamic parameters to enable editing of elements in the simulation model output file, or to establish a synchronization port to achieve synchronous updates; the dynamic parameters are implemented through several function commands, including at least: search command function, read command function, compare command function, and set command function, and the function commands are created based on text command lines;

[0083] The search command function locates and searches elements in the simulation model output file through traversal search. The read command function reads data from different element types based on the location located by the search command function. The comparison command function analyzes and compares the read data with the updated data. The set command function reads system synchronization commands or preset storage commands to determine whether to update the read data.

[0084] The system simulation configuration file is used to configure system simulation settings parameters, including system simulation model decoder and encoder configuration, simulation parameter solver type, and model simulation control parameters;

[0085] The data management layer is mainly used to establish various databases to support the smooth execution of the functions of each component. According to the requirements, the data management layer in this application includes at least a power equipment model database and a power equipment fault database.

[0086] The power equipment model database is used to establish an effective 3D simulation data support library for power equipment. Considering the current database file format of power equipment simulation model software, to ensure the logic processing layer can utilize and extract the necessary simulation modeling data and achieve relatively realistic 3D model simulations, four elements should be fully defined: power equipment component models, model topology relationships, model forces, and model force element attributes. Therefore, based on actual needs, the modeling processing component should establish data tables based on the following four element classes: Component model category, used to define interacting model entities, including at least the main component models of the power equipment, and the power component assembly space or basic model; Topology relationship category, used to define the connection relationships between model entities, including at least fixed connections, rotational connections, linear motion connections, planar motion connections, and spherical motion connections; Model force category, used to define the interaction relationships between model entities, including two-entity interactions and multi-entity interactions; Force element attribute category, used to define the attributes of the interaction forces between model entities, including field forces, stress, elastic forces, and deformation forces.

[0087] Furthermore, to enrich the simulation modeling data storage structure and enable the extraction and saving of elements outside the aforementioned categories when necessary to meet the needs of further simulation analysis and achieve flexible configuration, attribute variables and attribute functions are further defined to complete the definition and editing of relationships and attributes. The attribute variables include: name, mass, inertia, connection relationship container, entity force container, force element container, position container, and direction container; the attribute variables are string data; the attribute functions include: force action function in each direction, torque action function in each direction, relationship writing function, data writing function, and data reading function.

[0088] The force and connection data between model entities in the model description file are stored in a variable container. The connection relationship can be edited by adding model entities to the container, which makes the conversion of model information easier. In particular, to improve reading efficiency, an additional container size variable is configured in practical applications to update the flag when the data in the container changes. During the reading of data in the container, the container size variable is used to determine whether all attribute variables have been read and processed, thereby simplifying the data processing flow.

[0089] The power equipment fault database is the foundation for realizing power equipment fault simulation analysis. In this application, the basic database of power equipment faults is mainly established by the cooperation of multiple relational sub-databases with different functional attributes. The relational databases are selected according to the system platform, and commonly used ones include Oracle, MySQL, Microsoft SQL Server, Sybase SQL Server, Informix, etc. The sub-databases include fault management database, rule condition database, rule result database, fault instance database, and code database.

[0090] The fault management library is used to store basic fault content codes, fault indicator codes, and auxiliary description codes. The basic fault content codes refer to the basic fault content descriptions stored in text form, the fault indicator codes refer to the fault type indicator codes established based on preset coding rules, and the auxiliary description codes refer to auxiliary information data stored in text form.

[0091] The rule condition library is used to store data codes and their encodings related to fault conditions, fault results, and fault simulation methods; the data codes and their encodings are stored in the form of numbers and text characters;

[0092] The rule judgment library is used to store the rules that lead to different fault results under different fault conditions. The fault condition codes in the rule condition library are combined with logical operators to generate judgment rules for different fault results and establish the identification codes for different judgment rules.

[0093] Furthermore, considering that this application is mainly used for basic fault simulation demonstration and modeling of power equipment, and does not require analysis and processing of relatively complex fault principles and long-term continuous processes, in order to simplify the structure of the power equipment fault database, compress the data volume, and reduce the cost of database generation, use, and maintenance, this application mainly adopts generative rules to establish the rule judgment library.

[0094] The basic rule form in the rule base is as follows Where A refers to the fault condition in the rule condition library. Or its combination, in the combination This means simultaneously satisfying, B refers to satisfying one of the following; B refers to the fault result and its combination. It means Credibility;

[0095] Furthermore, to establish a comprehensive rule base, it also includes steps for extracting and generating rules from the rule base, including...

[0096] 1. Establish a fault tree for power equipment. Specifically, this means establishing a fault dataset for power equipment based on the definition of fault status and fault type, determining the causes and occurrence paths of various faults, and identifying the highest-level fault as the top-level fault based on the judgment of fault paths and faults.

[0097] 2. Based on the requirements of the power equipment fault simulation system, sort out the system fault states, ignore low-probability events with low impact, and determine the fault tree range boundary; complete the accurate definition of all fault conditions, sort out the logical relationships under fault conditions, and draw a complete fault tree;

[0098] 3. Extract power equipment fault rule conditions based on the hierarchical relationships between fault tree structures and generate a rule base;

[0099] The fault instance library is established based on the fault content, judgment rules, and corresponding fault instances in the aforementioned sub-databases, and also saves data such as the corresponding fault troubleshooting methods.

[0100] The code repository is used to store and manage various relational functions and rule definition functions required for content editing and data processing in each sub-database;

[0101] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and are not intended to limit the scope of protection of the present invention. Although the present invention has been described in detail with reference to preferred embodiments, those skilled in the art should understand that modifications or equivalent substitutions can be made to the technical solutions of the present invention without departing from the essence and scope of the technical solutions of the present invention.

Claims

1. A power equipment fault simulation analysis and modeling system, characterized in that, It should include at least an interaction layer, a logic processing layer, and a data management layer; The interaction layer includes model editing interaction components, simulation interaction components, and interaction control components; The model editing interactive component is used to retrieve the 3D model simulation data generated by the modeling processing component, and to generate power equipment simulation relationship data based on the simulation topology connection relationship of the 3D model generated by the simulation parameter editing component. The simulation interaction component is used to retrieve the simulation information stored in the power equipment model database and equipment simulation template library in the data management layer based on the 3D model simulation relationship data generated by the model editing interaction component, and generate corresponding simulation expression data. Interactive control components are used to establish interface controls and mapping tables between interface controls and specific functions and interactive actions using visual and graphical controls. The logic processing layer includes modeling processing components, simulation parameter editing components, and import / export components; The modeling processing component is used to read the interactive operation content obtained by the interactive control component and perform logical operation processing on the simulation model according to the interactive operation category. The simulation parameter editing component is used to read the interactive operation commands obtained by the interactive control component, decode the simulation model operation content corresponding to the interactive control commands, and traverse and extract the simulation entity objects and simulation operation content in the operation content through nested loop retrieval. It retrieves three-dimensional model data units of different formats from the power equipment model database and extracts the simulation parameters in the three-dimensional model; it retrieves three-dimensional graphic data of different formats, extracts the geometric and material property information corresponding to the three-dimensional model units, and establishes the mapping relationship between three-dimensional model units, property information, and simulation entities. Import / export components are used to establish standardized simulation models, simulation parameter data extraction and storage mechanisms that automatically match the required format, and to configure file classes for input and output data in the corresponding formats; including simulation model output files and system simulation configuration files; The simulation model output file is used to save the output signals, output list, and output data; the system simulation configuration file is used to configure the system simulation settings parameters, including the system simulation model decoder and encoder configuration, simulation parameter solver type, and model simulation control parameters. The data management layer includes a power equipment model database and a power equipment fault database; The power equipment model database is used to define power equipment component models, model topology relationships, model forces, and model force element attributes. The power equipment fault database is established using a relational database to create a fault management database, a rule condition database, a rule result database, a fault instance database, and a code database.

2. The power equipment fault simulation analysis and modeling system according to claim 1, characterized in that, The fault management library is used to store basic fault content codes, fault flag codes, and auxiliary description codes; The rule condition library is used to store data codes and their encodings related to fault conditions, fault results, and fault simulation methods; the data codes and their encodings are stored in the form of numbers and text characters; The rule judgment library is used to store the rules that lead to different fault results under different fault conditions. The fault condition codes in the rule condition library are combined with logical operators to generate judgment rules for different fault results and establish the identification codes for different judgment rules. The fault instance library is established based on the fault content, judgment rules, and corresponding fault instances in the aforementioned sub-databases, and also saves data such as the corresponding fault troubleshooting methods. The code repository is used to store and manage various relational functions and rule definition functions required for content editing and data processing in each sub-database.

3. The power equipment fault simulation analysis and modeling system according to claim 1, characterized in that, The logic processing layer is used for data extraction and data transmission processes, specifically including: a1. The steps of source data acquisition refer to setting at least one neutral format file, and based on targeted data extraction, performing preliminary standardization and classification of simulation model data files that may be involved in the simulation modeling process, so as to facilitate the execution of a relatively unified data extraction process. a2. Simulation model data extraction: Parse the simulation model data in the neutral format file, and use the built-in query function of the system platform to extract the required model parameters from the simulation model data. a3. The generalized expression of model parameters refers to unifying the units, symbols, and expressions of various model parameters through function transformation and storing them in the generalized expression database of models. a4. Model parameter extraction refers to extracting the required model parameter data from the general model database as needed by defining assignment functions and extraction functions, and configuring a neutral model parameter table that matches the aforementioned neutral format file. a5. Model simulation association refers to parsing the model parameter table, generating model parameters for simulation, and passing them to the modeling processing component.

4. The power equipment fault simulation analysis and modeling system according to claim 3, characterized in that, A neutral format is established based on a line command file with standardized descriptive syntax rules, where each line of command represents the interactive operation content for a model entity; The specification describes the syntax rules consisting of object text representing model entities, action text representing interaction operation categories, and parameter text representing specific attribute values ​​of interaction operations. The object text consists of several model entity IDs or codes, the action text consists of several operation names, and the parameter text consists of operation parameters that match each operation type. Dedicated line continuation characters are configured to determine the content boundaries of each command line, and comment characters are configured to distinguish between command lines and non-command lines. The neutral format file uses predefined fixed tag elements in the text document to save simulation model parameter data. The predefined tag elements in the text document include at least: Version and encoding tags: These are used to declare the document version and encoding type tags, so as to standardize the definition of subsequent tag elements and functions in the text document. They are usually placed at the very beginning of the text document to determine the standard on which the text document is based at the first time. Entity Root Label: Used to define the object that serves as the root simulation entity in the nested relationship of the simulation model. The root simulation entity refers to the object used as the reference for the position and connection relationship of each entity during the model saving process, which is used to quickly locate the reference and realize the location and relationship analysis of simulation entity information. Sub-entity tag: Used to define the master-slave nesting of the simulation model. The master-slave nesting refers to the relationship between two simulation entities that are at different levels in the nesting relationship of the simulation model expressed based on a tree structure.

5. The power equipment fault simulation analysis and modeling system according to claim 1, characterized in that, The simulation model output file also uses dynamic parameters to enable editing of elements in the simulation model output file, or to establish a synchronization port to achieve synchronous updates; the dynamic parameters are implemented through several function commands, including at least: search command function, read command function, compare command function, and set command function, and the function commands are created based on text command lines; The search command function locates elements in the simulation model output file through traversal search. The read command function reads data from different element types based on the location located by the search command function. The comparison command function analyzes and compares the read data with the updated data. The set command function reads system synchronization commands or preset storage commands to determine whether to update the read data.

6. The power equipment fault simulation analysis and modeling system according to claim 1, characterized in that, The output signal refers to the ID, output format, and saving method of the simulation model output signal determined by file parameters or instructions; The output list refers to the list of output signal IDs, overload IDs and their overload counts stored in a linked list, which is used to realize the batch import and export of simulation models and improve the efficiency of reading repetitive parts. The output file class refers to the model simulation data and its file storage information saved through predefined neutral files. The file storage information includes the actual path of the simulation model output file, the ID of the simulation model output file, and the storage status flag parameter of the simulation model output file. The storage status flag parameter is used to mark the storage update status of the simulation model output file to determine whether to maintain storage space and ensure the effective storage of the simulation model output file.

7. The power equipment fault simulation analysis and modeling system according to claim 1, characterized in that, The power equipment model database is used to create data tables based on four element classes, specifically including: Component model category, used to define the interacting model entities, including at least the main component models of the power equipment, the power component assembly space or basic model; Topological relationship categories are used to define the connection relationships between model entities, including at least fixed connections, rotational connections, linear motion connections, planar motion connections, and spherical motion connections; The model force category is used to define the interaction relationships between model entities, including two-entity interactions and multi-entity interactions; Force element attribute categories are used to define the properties of the interaction forces between model entities, including field forces, stress, elastic forces, and deformation forces.

8. The power equipment fault simulation analysis and modeling system according to claim 1, characterized in that, Generative rules are used to build a rule decision base. The basic rule form in the rule base is as follows: Where A refers to the fault condition in the rule condition library. or combinations thereof In the combination This means simultaneously satisfying, B refers to satisfying one of the following; B refers to the fault result and its combination. It means Credibility.

9. The power equipment fault simulation analysis and modeling system according to claim 1, characterized in that, To establish a comprehensive rule base, the process also includes steps for extracting and generating rules from the rule base. b1. Establishing a fault tree for power equipment: Specifically, based on the definition of fault status and fault type of power equipment, establish a fault dataset for power equipment, determine the causes and occurrence paths of various faults, and on the basis of judging the fault path and fault, determine the highest level fault as the top-level fault. b2. Based on the requirements of the power equipment fault simulation system, sort out the system fault states, ignore low-probability events with low impact, and determine the fault tree range boundary; complete the accurate definition of all fault conditions, sort out the logical relationships under the fault conditions, and draw a complete fault tree; b3. Extract power equipment fault rule conditions based on the hierarchical relationship between fault tree structures and generate a rule base.

10. The power equipment fault simulation analysis and modeling system according to claim 1, characterized in that, To enrich the data storage structure for simulation modeling, attribute variables and attribute functions are defined to complete the definition and editing of relationships and attributes. The attribute variables include: name, mass, inertia, connection relationship container, entity force container, force element container, position container, and direction container; the attribute variables are string data; the attribute functions include: force action function in each direction, torque action function in each direction, relationship writing function, data writing function, and data reading function. To improve reading efficiency, a container size variable is configured to update the flag when the data within the container changes. During the data reading process within the container, the container size variable is used to determine whether all attribute variables have been read and processed, thereby simplifying the data processing flow.

Images