Modularized multiplexing method for coal mine electromechanical equipment model

Abstract

The invention discloses a modularized multiplexing method for a coal mine electromechanical equipment model. The core of the method is that a three-level object model architecture composed of a public information layer, an extended information layer and a combined information layer is established; the public information layer is used for defining a universal attribute set of all equipment models through atomization division and carrying out standardized coding on the universal attribute set; the extended information layer is used for describing an attribute set of specific states and functions of equipment model categories, and adopts an independent storage structure decoupled from the public information layer; and the combined information layer is used for freely combining attributes defined in the public information layer and the extended information layer through a dynamic coding rule to generate a combined attribute set. According to the embodiment of the invention, derivation and cross-class recombination of the model are realized through logic superposition operation, and standardized access of the multi-source heterogeneous industrial protocol is realized by utilizing the object model triple, so that the model development efficiency and the reuse rate are improved, the system compatibility and the data standardization degree are enhanced, and meanwhile, the iteration cost is reduced.

Description

Technical Field

[0001] Applications generally involve digital modeling technology for coal mines, and in particular, a modular reuse method for coal mine electromechanical equipment models. Background Technology

[0002] With the advancement of smart mine construction, digital modeling of underground electromechanical equipment in coal mines has become the foundation for realizing remote mining, collaborative mining, and refined management. However, due to the lack of historical standards, current coal mine electromechanical models generally suffer from problems such as chaotic modeling, coarse attribute granularity, and insufficient model scalability. While existing standards (such as the NB / T11118 series) provide some specifications for equipment object models, their model library has a coarse granularity and mostly adopts a single-unit modeling approach. Each equipment model needs to independently define all attributes and parameters, resulting in high coupling of model attributes and poor reusability. Therefore, it is difficult to support modular construction and standardized reuse of object models in a "building block" manner, and it cannot meet the needs of rapid access of multi-brand and multi-protocol equipment and cross-system data fusion, thus restricting the further improvement of the level of coal mine intelligence.

[0003] Chinese Patent Publication No. CN107993283A discloses a method for constructing transparent mines. Although it has made progress in achieving integrated and dynamic updates of geological bodies, roadways, and equipment models, its technical focus is on the construction of macroscopic scenes and the spatial integration and topological association between different model categories. However, the model construction method is rigid and lacks modular reusability. Furthermore, it does not perform atomic division and standardized coding of equipment model attributes, resulting in coarse attribute granularity. Due to the high coupling of internal attributes, when equipment parameters change or functions are expanded, the entire model needs to be fully modified and reconstructed, leading to high iteration costs and poor flexibility. It also does not address how to map and manage equipment data under multi-source heterogeneous industrial protocols through a unified and standardized identification system. This results in the need to develop a large amount of customized protocol parsing code when accessing devices with different protocols, thus restricting system compatibility and scalability. Summary of the Invention

[0004] This application provides a modular reuse method for coal mine electromechanical equipment models to address some of the deficiencies mentioned in the background art.

[0005] In a first aspect, embodiments of this application provide a method for modular reuse of coal mine electromechanical equipment models, comprising: A physical model of coal mine electromechanical equipment was established. The physical model adopts a three-level architecture, including a common information layer, an extended information layer, and a combined information layer. The common information layer is used to define a common set of attributes for all device models through atomic partitioning, and to standardize and encode them to establish a template library of basic device attributes.

[0006] The general attribute set includes, but is not limited to, the device basic attribute set, the device network attribute set, and the device location attribute set.

[0007] The extended information layer is used to describe the attribute set of the unique state and function of the device model category. It adopts an independent storage structure decoupled from the public information layer to achieve differentiated attribute modeling.

[0008] Preferably, the extended information layer uses XML format to store the extended attribute set, and each functional module corresponds to an independent namespace.

[0009] The composite information layer is used to freely combine the attributes defined in the public information layer and the extended information layer through dynamic coding rules to generate a composite attribute set, thereby improving the interoperability efficiency between devices.

[0010] The combined attribute set generated by the combined information layer is particularly suitable for combining attributes that need to be read or controlled simultaneously in a predetermined order.

[0011] Preferably, the modular reuse method for coal mine electromechanical equipment models in this application embodiment further includes a model reuse step: based on a predefined equipment model code, at least one common information model code and at least one extended information model code are combined through logical superposition operations to derive a target equipment model.

[0012] Preferably, the logical superposition operation supports operator operations, and the result encoding can be appended with a version check code to achieve version control.

[0013] Preferably, the model reuse step supports cross-class reorganization, such as grafting the extended attributes of the power supply switch into the water pump model to enable the water pump to have power supply protection function.

[0014] Preferably, the modular reuse method for coal mine electromechanical equipment models in this application embodiment further includes a protocol adaptation step: The device point table addresses in industrial protocols (such as Modbus TCP / IP) are converted into object model triples for unified identification and processing, thereby enabling standardized access to multi-source heterogeneous protocols.

[0015] Compared with the prior art, the beneficial effects of the present invention include: Improved development efficiency: Through modular reuse and a "building block" model building approach, the average model building time was reduced from 8 person-days to 2 person-days; Improved model reusability: Common attribute sets and method sets can be shared by different devices, solving the problems of high coupling and low reusability in traditional models; Reduced iteration costs: When device parameters change, only the corresponding attribute modules need to be modified, avoiding the reconstruction of the entire model; Enhanced compatibility and scalability: Through object model triples and dynamic coding mechanisms, it supports mixed orchestration and adaptation of multiple mainstream industrial protocols such as Modbus / TCP, EtherNet / IP, OPC UA, and Profinet, and can easily integrate new sensors and devices; The standardization of data has been improved: unified coding rules and attribute division have reduced the field conflict rate of the mine equipment model from 18% to 1.2%, laying the foundation for cross-system data fusion. Attached Figure Description

[0016] Figure 1 This is a schematic diagram of the three-level architecture of the object model in the embodiments of this application; Figure 2 This is a schematic diagram of the common attribute set of the power supply circuit in an embodiment of this application; Figure 3 This is a schematic diagram illustrating the information included in the device according to an embodiment of this application; Figure 4 This is a schematic diagram of the special attribute set of the high-voltage vacuum switch in an embodiment of this application; Figure 5 This is a schematic diagram of the relay protection model method set in the embodiments of this application; Figure 6 This is a schematic representation of the high-voltage vacuum switch combination information encoding in the embodiments of this application; Figure 7 This is a structural diagram describing the combined information attributes in an embodiment of this application; Figure 8 This is a schematic diagram illustrating a model reuse method according to an embodiment of this application; Figure 9 This is a schematic diagram of the "building block" method for combining and reusing models in the embodiments of this application; Figure 10 This is a schematic diagram of the coal mining machine model design according to an embodiment of this application; Figure 11 This is a schematic diagram of the physical model structure of an embodiment of this application; Figure 12 This is a flowchart illustrating the data acquisition and management using object model triples in an embodiment of this application. Figure 13 This is an interactive diagram illustrating the object model reading service in an embodiment of this application. Figure 14 An interactive diagram illustrating the service settings for the object model in the embodiments of this application; Figure 15 An interactive schematic diagram serving the object modeling method of the embodiments of this application. Detailed Implementation

[0017] The present application will now be described in further detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the application and not intended to limit it. Furthermore, it should be noted that, for ease of description, the accompanying drawings show only the parts relevant to the present application, not the entire structure.

[0018] This invention constructs a modular and reusable model system for coal mine electromechanical equipment. (See also...) Figure 1 As shown, the object model system of the present invention adopts a three-level architecture consisting of three types of information: "public information", "extended information" and "combined information". In order to systematically organize and manage these information modules and realize their flexible "building block" combination, the present invention establishes a unified coding system, which covers device type, device model and device instance from top to bottom.

[0019] As a preferred implementation method, the macro-classification of equipment types and their coding rules are shown in Table 1 below: Table 1 Equipment Type Coding Table

[0020] Under the category of equipment, this invention further defines encoding rules for the specific models constituting the equipment; as shown in Table 2 below, the rules clarify the encoding range of different levels of models such as public information model, industry public information model and equipment-specific information model, and these model codes are the basic operands for subsequent logical superposition operations to combine into specific equipment.

[0021] Table 2 Equipment Model Coding Table

[0022] Finally, in practical applications, an abstract model can be instantiated into multiple concrete equipment entities, which is a direct manifestation of model reuse. Table 3 below uses a coal mining machine as an example to specifically demonstrate how the same model, such as a motor model, can be reused by multiple equipment components through different instance encodings.

[0023] Table 3 Equipment Instance Coding Table

[0024] Based on the above coding system, the following section will elaborate on how to ultimately complete the abstract description of the device and the standardized access of the protocol through the specific construction and combination of the three-level architecture.

[0025] Regarding the construction process of the public information layer, public information is used to define a common attribute set for all device models, establish a basic attribute template library for devices, and decompose basic attributes into indivisible minimum data units through atomic partitioning, followed by standardized coding; for example, The "Equipment Basic Model" (coded as 0x0001) includes the equipment's name, manufacturer, status, version information, etc. The “Device Network Model” (encoded as 0x0002) contains a set of network attributes required for devices to connect to the network, such as IP addresses, subnet masks, and communication protocols. The "equipment location model" (coded as 0x0003) contains information such as the equipment's installation location and coordinates underground; As shown in Table 2, these common models are assigned unique standardized codes, serving as the basic units for model combination; see also Figure 2 As shown, Figure 2 Taking a power supply circuit as an example, the composition of its common attribute set is specifically demonstrated. This includes basic attributes such as rated voltage, rated current, and power factor that are shared by various power supply equipment, reflecting the atomization and standardization design concept of the common information layer.

[0026] Regarding the construction process of the extended information layer, extended information is used to describe attribute sets that describe the unique states and functions of equipment model categories, achieving differentiated attribute modeling. A functional decoupling design is adopted; for example, extended attribute sets are stored in XML format, and each functional module corresponds to an independent namespace to ensure separation from public information. For instance, attributes unique to power supply switches, such as the "leakage current blocking threshold," and those unique to mobile substations, such as the "harmonic distortion rate," are defined as independent extended models and encoded (e.g., 0x207E). The relationship between public information and extended information is as follows: Figure 3 As shown.

[0027] See Figure 4 As shown, Figure 4 This demonstrates a specific implementation of the special attribute set of a high-voltage vacuum switch, including unique attributes such as "short-circuit protection current setting value" and "leakage current blocking resistance value".

[0028] The composite information layer is key to achieving modular reuse. Through dynamic encoding rules, it freely combines attributes defined in the common and extended information layers to generate composite attribute sets tailored to specific business scenarios, thereby improving interoperability efficiency between devices. To achieve flexible model combination, this invention develops an attribute encoding engine that supports the use of logical superposition operators (+, -, *) to perform operations on model encoding. The operator "+" indicates adding a new functional module or attribute set to the basic model; the operator "-" indicates removing a default functional module or attribute set from the basic model that is not currently needed by the device; and the operator "*" indicates that multiple attribute sets need to be configured or distributed as a whole. Through these operations, model derivation and cross-class recombination can be achieved. The attribute description structure of the composite information is as follows: Figure 7 As shown.

[0029] See Figure 6As shown, the water pump's main function is "drainage," but to achieve switch protection attributes, the common relay protection model of the feeder switch needs to be reused. If conflicts exist, manufacturers should instantiate equipment model instances that meet their own needs according to the defined equipment model rules. Manufacturers can also appropriately add equipment extension information and equipment combination information that meet third-party extension requirements. For example, a coal mining machine has two cutting sections, left and right, each with a motor. When calling the motor model, it's necessary to distinguish between left and right, so the motor needs to be instantiated twice. The instances are represented by combination coding to resolve the "conflict" issue. The specific instantiation rules are as follows: One or more device instances can be generated for the same device model; A unique instance ID should be generated for each instance in a device model instance; this ID is set by the device manufacturer during the device instantiation process, and this standard recommends using an integer starting from 1 and incrementing to identify the ID; The device model instance must include the device common information attribute set and the device extended information attribute set, which are explicitly "required" items during the model definition process; When instantiating a device instance, all instantiated property values ​​should be initialized to zero unless default values ​​are specified in the device property definition. The attribute set codes, attribute names, attribute IDs, attribute types, whether they are required, and access permissions of the device information are clearly defined and cannot be modified; manufacturers can define the required attributes, attribute types, and access permissions themselves according to the data model specifications in the reserved and extended sections. Attributes with explicitly defined access permissions should provide a way to read or write them; According to their own needs, and provided that they comply with the data model specifications, new attributes can be defined in the reserved area and the custom extension area; however, metadata such as attribute set encoding, attribute ID, attribute type, and access permissions that are clearly defined in the standard information model cannot be modified by the vendor during instantiation.

[0030] A device instance typically inherits the set of extended attributes defined by its corresponding device model. If you want to introduce extended attributes of other device types through "cross-class recombination", you need to perform a legal combination at the model level through the aforementioned logical superposition operation, rather than arbitrarily adding undefined attributes during the instantiation process.

[0031] There is only one public information agreement for a device, therefore, there is only one instance of each of the three attribute sets in the public information: the device basic attribute set, the network attribute set, and the location attribute set.

[0032] See Figure 5 As shown, Figure 5An example of a common method set is shown, namely the relay protection model method set, which contains common commands such as "protection enable / disable" and "reset" that can be invoked by multiple devices.

[0033] See Figure 6 As shown, Figure 6 This provides a specific embodiment of the combined information layer, demonstrating how the uplink analog signals of a high-voltage vacuum switch organize multiple attributes (such as A / B / C phase voltages) into an efficient combined attribute set through combined coding rules.

[0034] An example of model derivation is provided below: Common model of power supply switch (0x1001+0x1002+0x1003) + extension module (0x207E) = type A power supply switch (0x00000402); Through the above encoding operation, the specific device model can be quickly derived. To support iteration, a version check code can be appended to the end of the combined code, such as 010101-V2. Table 4. Model Information Attribute Set Definition Table

[0035] Referring to Table 4, the version control process during system operation is as follows: After establishing a connection with the device, the system first reads its 0x0000 attribute set to obtain readable metadata such as the model version number; the system calculates the version check code in real time based on the model code reported by the device (such as 0x00000402) and its current configuration; the calculated check code is compared with the check code preset in the device model or the previously stored check code: if they match, it is determined that the model has not changed and is processed according to the existing logic; if they do not match, it is determined that the model has been updated, and an alarm can be triggered, a request to update the parsing logic can be made, or compatibility processing can be performed based on the version information in the 0x0000 attribute set.

[0036] To support model iteration, this invention introduces a version control mechanism; the device model contains version-related attributes (such as the model version number located in the 0x0000 attribute set); when the system establishes a connection with the device via an industrial control protocol (such as MDTP), it first reads these version attributes for identification and compatibility checks; model updates can be achieved through predefined methods in its method set; such as... Figure 5 and Figure 1 As shown, the entire device is composed of a common model and an extended model in a "building block" manner; while the combined encoding provides a unified addressing identifier for upper-layer applications, which is used to implement read / write operations on specific attributes.

[0037] An example of cross-class refactoring is provided below, in which the extended attributes (protection function) of the power supply switch are logically superimposed onto the common model of the water pump, enabling the water pump model to have power supply protection function, realizing cross-device reuse of function, and the attribute description structure of the combined information is as follows: Figure 7 As shown.

[0038] The reuse mechanism of this invention is reflected in the fact that different devices can share the same abstract model, such as Figure 8 and Figure 9 As shown, the cutting motor, hydraulic support motor, and scraper conveyor motor of the mining roadheader can share a single "motor model" (code 0x1200). The entire equipment is constructed from multiple such minimal functional set models, like building blocks. Figure 10 The coal mining machine model design shown clearly demonstrates how to combine multiple functional modules such as the "cutting section model", "traction section model", and "hydraulic system model" into a complete coal mining machine equipment model, which is a macroscopic embodiment of the "building block" construction concept.

[0039] See Figure 11 As shown, Figure 11 The diagram shows the object model structure of the present invention. As shown in the figure, the object model triple is composed of model ID 1101, instance ID 1102 and attribute ID 1103 connected in sequence. This triple serves as a unified data identifier and forms a mapping relationship with the specific point table address (such as Modbus address 40001) in the industrial protocol, thereby shielding the differences in the underlying protocol.

[0040] To achieve unified access for multi-source heterogeneous devices, this invention uses object model triples to adapt to different industrial protocols. (See reference...) Figure 12 As shown, Figure 12 The complete flowchart of data acquisition and management using triples is shown; the following uses the Modbus TCP / IP protocol as an example to explain the data acquisition and reading process in detail: Step 1: In the protocol service, parse the XML file of the device object model, extract the model, device, network, and function information, and store it in memory (such as std::vector); Step 2: Register the parsed model information through the protocol stack interface, which is HcpRegisterAttributeSet; Step 3: Start services such as MODBUS, connect to the device, and listen for data; Step 4: Register the callback function to the MODBUS service; Step 5: The MODBUS client collects data, formats it as a JSON string, and uploads it. The JSON string is like {"0x1003.0x0001.0x0038":"36"}; Step 6: The protocol service receives the JSON data and updates the corresponding data in memory based on the triples; Step 7: When the application requests data, return the latest data in memory to the application through the interface and callback function. The interface can be HcpReadRemoteAttrValue, and the callback function can be OnReadCallback. Step 8: Apply the displayed data to complete one attribute reading.

[0041] Based on the aforementioned basic data interaction, the object model of this invention also provides rich service interfaces for upper-layer applications; Figure 13 The interaction sequence of the object model reading service is obtained by asynchronously reading device attributes by calling the readRemoteAttrValue interface; Figure 14 The diagram illustrates the interaction sequence of the object model setting service. The application sets device attributes by calling the writeRemoteAttrValue interface, the underlying protocol stack sends instructions to the device, and returns the execution status through a callback function. Figure 15 The diagram illustrates the interaction sequence of the object model method service, where the application executes the remote device's method by calling the methodCall interface.

[0042] In this embodiment, a remote device attribute setting request is registered to write attribute values ​​into a specified model of a specified device. When this function is called, the underlying protocol stack sends a write attribute command to the device and returns the execution status through a callback function after the operation is completed. That is, when the user inputs parameters, HcpRegisterAttributeSet is called to send a command and receive a response. The device returns the operation result, which is then processed by a callback and returned to the upper-layer application. For example, when the user inputs parameters such as modelId=4121, instanceId=62, attrId=8 through the interface, HcpRegisterAttributeSet is called. The system encapsulates these parameters into a structure, calls this function, sends a command and receives a response, that is, sends a writeRemote command to the device through the protocol stack, and the device returns the operation result, such as: json {"attrResultList":{"modelId":4121,"modelInstanceId":1,"attrid":62,"writeStatus":2}}; Then call the callback function from the registration point to return the result to the upper-layer application.

[0043] By adopting the method of adapting physical model triples to different industrial protocols in this embodiment, upper-layer applications only need to process the unified triples without having to worry about the complex protocol details at the lower level, thus achieving "modeling once, universal application everywhere".

[0044] This embodiment provides an example of an XML-based configuration file to illustrate how to establish a mapping relationship from industrial protocol addresses to object model triples. The configuration file mainly includes two parts: interface channel configuration and data point mapping configuration. Interface channel configuration: Used to define the parameters of the physical or logical communication interface, as shown in Listing 1, which defines a MODBUS-RTU communication channel.

[0045] Data point mapping configuration: This is the core of protocol conversion; each <item>The element atomically defines a mapping rule between a MODBUS data point and an object model triple (attrSetId, attrSetInstanceId, attrId), and may include data transformation rules (such as LinearScale).

[0046] By parsing this configuration file, the protocol adaptation service can establish a communication link and load all mapping rules at startup; during data acquisition, the service automatically transforms the acquired raw data (such as register integer values) according to the defined transformation rules (such as linear transformation) based on this configuration. The calculation is performed and finally updated to the memory data object uniquely identified by the triple (attrSetId.attrSetInstanceId.attrId).

[0047] Listing 1: Interface Channel Configuration Example <interfaceinstance id="2"> <baseinfo> <item name="interface" value="modbus-serial00" / > <item name="protocol" value="MODBUS_RTU" / > <item name="isClient" value="true" / > <item name="MODBUS_RTU" serial=" / dev / ttyS0" baudrate="9600" checkbit="None" databit="8" stopbit="1" / > < / baseinfo> <!-- Data point mapping is shown in Listing 2 --> < / interfaceinstance> Listing 2 Data Point Mapping Configuration <datapoints> <item id="0x0001" itemname="sbyybyl_001" slaveid="3" readopcode="0x04" address="0x40000" registercount="1" access="WR" attrSetId="4" attrSetInstanceId="1" attrId="1" transformType="LinearScale" transformParams="{'k': 0.0025, 'b': -10}" / > <item id="0x0002" itemname="sbyybll_002" slaveid="3" readopcode="0x04" address="0x40001" registercount="1" access="WR" attrSetId="4" attrSetInstanceId="1" attrId="2" transformType="LinearScale" transformParams="{'k': 0.02084, 'b': -83.35}" / > <!--... More data points... --> < / datapoints> < / item>

Claims

1. A modular reuse method for coal mine electromechanical equipment models, characterized in that, include: A physical model of coal mine electromechanical equipment is established. The physical model adopts a three-level architecture, including a common information layer, an extended information layer, and a combined information layer. The common information layer is used to define a common attribute set for all device models through atomic partitioning and to standardize its encoding; The extended information layer is used to describe the attribute set of the unique state and function of the device model category, and adopts an independent storage structure decoupled from the public information layer; The combined information layer is used to freely combine the attributes defined in the public information layer and the extended information layer through dynamic encoding rules to generate a combined attribute set.

2. The modular reuse method for coal mine electromechanical equipment models according to claim 1, characterized in that, Also includes models Reuse steps: Based on a predefined device model code, at least one common information model code and at least one extended information model code are combined through logical superposition operations to derive the target device model. The logical superposition operation supports operator operations.

3. The modular reuse method for coal mine electromechanical equipment models according to claim 2, characterized in that, The logical stack The result of the addition operation is encoded and appended with a version checksum to achieve version control.

4. The modular reuse method for coal mine electromechanical equipment models according to claim 2, characterized in that, The model complex The steps also include cross-class recombination: The extended information model of the first device type is grafted onto the common information model of the second device type through logical superposition operation, so that the second device model has some of the functions of the first device type.

5. The modular reuse method for coal mine electromechanical equipment models according to claim 1, characterized in that, Also includes protocols Adaptation steps: The device point table address in the industrial protocol is converted into a physical model triple for identification and processing; The structure of the object model triple is: modelID.instanceID.attributeID.

6. The modular reuse method for coal mine electromechanical equipment models according to claim 5, characterized in that, The protocol is applicable The preparation steps specifically include: Parse the device model file, extract model information, and register it through the protocol stack interface; Start the protocol service, collect device data and format it into a standardized data string containing the object model triples and their corresponding values; Receive and parse the standardized data string, and update the data object in memory based on the triplet information therein; In response to a data request from an application, the data corresponding to the requested triplet in the data object is returned through the protocol stack interface.

7. The modular reuse method for coal mine electromechanical equipment models according to claim 1, characterized in that, The common attribute set defined by the public information layer includes at least one of the device basic attribute set, the device network attribute set, and the device location attribute set.

8. The modular reuse method for coal mine electromechanical equipment models according to claim 1, characterized in that, The extended information layer uses XML format to store extended attribute sets, and each functional module corresponds to an independent namespace.

9. The modular reuse method for coal mine electromechanical equipment models according to claim 1, characterized in that, The combined attribute set generated by the combined information layer is used to combine attributes that need to be read or controlled simultaneously in a predetermined order.

10. The modular reuse method for coal mine electromechanical equipment models according to any one of claims 1-9, characterized in that, The models in the device model library constructed by the method are distinguished and arranged according to the characteristics of static and dynamic attributes, real-time and non-real-time data, and control and non-control categories.

Images