A device monitoring data collection method and device, electronic device and storage medium

Abstract

This application provides a method, apparatus, electronic device, and storage medium for acquiring device monitoring data. The method includes: selecting a target protocol plugin from a variety of preset protocol plugins that matches the protocol type of the device to be connected, where each preset protocol plugin serves as a communication interface plugin for a specific protocol type. The target protocol plugin includes a parameter configuration file and a driver file, with the parameter configuration file containing data acquisition parameters; providing the data acquisition parameters from the parameter configuration file on a graphical user interface; determining the acquisition information of the device to be connected in response to a numerical adjustment operation of the data acquisition parameters; and running the driver file in response to a plugin execution command to acquire monitoring data from the device to be monitored based on the acquisition information, and providing the monitoring data on the graphical user interface. By employing the above-described method, apparatus, electronic device, and storage medium for acquiring device monitoring data, the scalability of the protocol plugin is improved.

Description

Technical Field

[0001] This application relates to the field of Internet of Things (IoT) technology, and more specifically, to a method, apparatus, electronic device, and storage medium for acquiring device monitoring data. Background Technology

[0002] With the rapid development of IoT technology, more and more devices are being connected to the Industrial Internet of Things (IIoT). These devices may use different communication protocols, such as Modbus (Modbus Protocol), UDP (User Datagram Protocol), and HTTP (Hypertext Transfer Protocol). Furthermore, even under the same communication protocol, different devices may have different protocol formats, data acquisition methods, and communication methods. Current technologies typically use hot-swapping technology to achieve real-time loading and unloading of protocol plugins. The core idea is to decouple the protocol processing module from the platform body using protocol plugins to meet the access needs of devices with different communication protocols.

[0003] However, existing device access methods still require modifying the protocol plugin code for new device models when dealing with devices that have the same communication protocol type but different device models, resulting in poor protocol plugin extensibility. Summary of the Invention

[0004] In view of the above, the purpose of this application is to provide a method, apparatus, electronic device and storage medium for acquiring equipment monitoring data, so as to overcome at least one of the above-mentioned defects.

[0005] In a first aspect, embodiments of this application provide a method for acquiring device monitoring data, the method comprising: For the device to be connected, a target protocol plugin that matches the protocol type of the device to be connected is selected from a variety of preset protocol plugins. Each preset protocol plugin is used as a communication interface plugin for a protocol type. The target protocol plugin includes a parameter configuration file and a driver file corresponding to the protocol type. The parameter configuration file contains data acquisition parameters. Provide data acquisition parameters from the parameter configuration file in the graphical user interface; In response to numerical adjustment operations on data acquisition parameters, determine the acquisition information of the device to be connected; In response to the plugin execution command, the driver file is run, and monitoring data is obtained from the device to be monitored based on the collected information, and the monitoring data is provided on the graphical user interface.

[0006] Optionally, the data acquisition parameters include multiple types, including a first data acquisition parameter for setting acquisition rules, a second data acquisition parameter for setting data transmission channels, and a third data acquisition parameter for setting communication protocols. The first data acquisition parameter is determined according to the device access method and acquisition requirements, the second data acquisition parameter is determined according to network and / or link requirements, and the third data acquisition parameter is determined according to the acquisition fields.

[0007] Optionally, each data acquisition parameter and multiple limiting parameters used to define that data acquisition parameter constitute a parameter group, and multiple parameter groups are configured in the parameter configuration file.

[0008] Optionally, each parameter group includes a verification parameter, and the method further includes: in response to a numerical adjustment operation, using the verification parameter to perform a validity check on the adjusted value of the data acquisition parameter; after passing the validity check, saving the adjusted value of the data acquisition parameter.

[0009] Optionally, the method also includes: determining the target monitoring items corresponding to the device to be connected based on the device model of the device to be connected; establishing a binding relationship between the target monitoring items and the data acquisition parameters to complete the configuration of device monitoring items for the device to be connected.

[0010] Optionally, before selecting a target protocol plugin from a variety of preset protocol plugins that matches the protocol type of the device to be accessed, the method further includes: obtaining the protocol plugin package of the target protocol plugin; parsing the protocol plugin package to obtain the parameter configuration file and driver file, wherein the driver file is compatible with all devices under the same protocol type; extracting the data acquisition parameters from the parameter configuration file to display the data acquisition parameters on the graphical user interface; and loading the driver file into the runtime environment to generate a callable communication driver unit.

[0011] Optionally, the method also includes: updating and upgrading the target protocol plugin through hot update to automatically load the updated parameter configuration file and driver file.

[0012] Secondly, embodiments of this application also provide a device for acquiring equipment monitoring data, the device comprising: The plugin acquisition module is used to select a target protocol plugin that matches the protocol type of the device to be accessed from a variety of preset protocol plugins. Each preset protocol plugin is used as a communication interface plugin for a protocol type. The target protocol plugin includes a parameter configuration file and a driver file corresponding to the protocol type. The parameter configuration file is configured with data acquisition parameters. The parameter display module is used to provide the data acquisition parameters in the parameter configuration file on the graphical user interface; The information determination module is used to determine the acquisition information of the device to be connected in response to the numerical adjustment operation of the data acquisition parameters. The device monitoring module is used to respond to the plug-in running instructions, run the driver file, obtain monitoring data from the device to be monitored based on the collected information, and provide the monitoring data on the graphical user interface.

[0013] Thirdly, embodiments of this application also provide an electronic device, including: a processor, a memory, and a bus. The memory stores machine-readable instructions executable by the processor. When the electronic device is running, the processor communicates with the memory via the bus. When the machine-readable instructions are executed by the processor, the steps of the device monitoring data acquisition method described above are performed.

[0014] Fourthly, embodiments of this application also provide a computer-readable storage medium storing a computer program, which, when executed by a processor, performs the steps of the device monitoring data acquisition method described above.

[0015] The embodiments of this application bring the following beneficial effects: This application provides a device monitoring data acquisition method, apparatus, electronic device, and storage medium that can use a unified driver file to meet the access requirements of different devices under the same protocol type. It also abstracts the data in the data monitoring process into parameters, so as to meet the different data acquisition parameter requirements of different device models under the same protocol type. There is no need to build separate protocol plugins for different device models, which improves the scalability of protocol plugins. Compared with the device monitoring data acquisition methods in the prior art, it solves the problem of low scalability of protocol plugins.

[0016] To make the above-mentioned objectives, features and advantages of this application more apparent and understandable, preferred embodiments are described below in detail with reference to the accompanying drawings. Attached Figure Description

[0017] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0018] Figure 1 A flowchart of the device monitoring data acquisition method provided in an embodiment of this application is shown; Figure 2 A schematic diagram of the structure of the equipment monitoring data acquisition device provided in an embodiment of this application is shown; Figure 3 A schematic diagram of the structure of the electronic device provided in the embodiments of this application is shown. Detailed Implementation

[0019] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. The components of the embodiments of this application described and shown in the accompanying drawings can generally be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of this application provided in the accompanying drawings is not intended to limit the scope of the claimed application, but merely represents selected embodiments of this application. Based on the embodiments of this application, every other embodiment obtained by those skilled in the art without inventive effort falls within the scope of protection of this application.

[0020] Based on this, this application provides a method for acquiring device monitoring data to improve the scalability of protocol plugins.

[0021] To facilitate understanding of this embodiment, the following description uses the device monitoring data acquisition method provided in this application embodiment applied to an industrial Internet of Things platform as an example to illustrate the above exemplary steps provided in this application embodiment.

[0022] Please see Figure 1 , Figure 1 This is a flowchart illustrating a device monitoring data acquisition method provided in an embodiment of this application. Figure 1 As shown in the embodiments of this application, the device monitoring data acquisition method includes: Step S101: For the device to be connected, select a target protocol plugin from a variety of preset protocol plugins that matches the protocol type of the device to be connected.

[0023] The device to be connected can refer to the device that is to be connected to the industrial Internet of Things (IIoT) platform. For example, the device to be connected can be a sensor or an instrument. After the device to be connected is connected to the industrial Internet of Things, it can collect and monitor the data of the device to be monitored.

[0024] The Industrial Internet of Things (IIoT) platform has a variety of preset protocol plugins. Each preset protocol plugin is used as a communication interface plugin for a certain protocol type. For example, there is a Modbus protocol plugin for the Modbus communication protocol, a UDP communication protocol plugin for the UDP protocol, and an HTTP protocol plugin for the HTTP communication protocol.

[0025] Each preset protocol plugin includes a parameter configuration file and a driver file. A single preset protocol plugin can adapt to different devices using that protocol type for communication. The driver file can refer to the plugin's business code file; one driver file adapts to all devices under the same protocol type. The driver file is used to adapt the device to be connected to a specific industrial communication protocol type. For example, the driver file in the Modbus protocol plugin adapts the device to be connected to the Modbus communication protocol; the driver file in the UDP protocol plugin adapts the device to be connected to the UDP communication protocol. The parameter configuration file contains data acquisition parameters, which abstract the relevant communication parameters required when collecting monitoring data from the monitored device.

[0026] In one example, to facilitate the maintenance and management of protocol plugins, each preset protocol plugin is managed independently and supports hot updates and hot-plugging.

[0027] For example, the target protocol plugin can be updated and upgraded via hot update to automatically load the updated parameter configuration file and driver file.

[0028] Data acquisition parameters include various types, including first data acquisition parameters, second data acquisition parameters, and third data acquisition parameters.

[0029] The first data acquisition parameter is used to set the acquisition rules. The first data acquisition parameter is determined based on the device access method and acquisition requirements. The access method can be a 485 bus access or a Modbus protocol access. For example, when using a Modbus access method, the first data acquisition parameter can be the acquisition period and acquisition frequency; when using a UDP-based access method, the first data acquisition parameter can be the request address, parameter ID, and parameter value. The first data acquisition parameter (also called the acquisition rule parameter) includes, but is not limited to: acquisition name, acquisition address, acquisition response time, polling interval, acquisition period interval, and maximum number of commands to be merged.

[0030] The second data acquisition parameters are used to set the data transmission channel. These parameters are determined based on network and / or link requirements. For example, if the network and / or link requirements are based on RTU (Remote Terminal Unit) communication, the second data acquisition parameters include IP address, port number, and channel type; if the communication is based on the HTTPS protocol, the second data acquisition parameters include request address, request type, and authentication method. The second data acquisition parameters (also known as channel parameters) include, but are not limited to: server port, server address, standby server address, standby server port, timeout period, and link type.

[0031] The third data acquisition parameter is used to set the communication protocol. The third data acquisition parameter is determined based on the acquisition field. For example, when the communication protocol is UDP, the third data acquisition parameter can be the data point name, data point number, data type, identification number, and information category; when the communication protocol is HTTP, the third data acquisition parameter can be the data point name, data point number, request parameters, parsing method, and parsing script. The third data acquisition parameter (also called protocol parameter) includes, but is not limited to: data point name, data type, data point grouping, address bit (addr), bit offset (subAddr), function code (funcCode), data type (dataType), byte order (dataOrder), and number of registers (num).

[0032] In practice, users first need to configure the basic monitoring information of the device to be connected, such as protocol type, link type, and target monitoring items for which data to be collected (e.g., temperature, humidity). After the user selects the device to be connected on the graphical user interface, the system queries a variety of preset protocol plugins to find the one that matches the protocol type and link type of the device to be connected, based on the device's basic monitoring information, and uses it as the target protocol plugin.

[0033] Step S102: Provide the data acquisition parameters from the parameter configuration file on the graphical user interface.

[0034] In practical implementation, the parameter configuration file contains multiple parameter groups. Each parameter group includes a data acquisition parameter and multiple limiting parameters used to define that data acquisition parameter. That is, each data acquisition parameter and multiple limiting parameters constitute a parameter group. The multiple limiting parameters include, but are not limited to: parameter ID, parameter type, parameter input type, parameter request, parameter unit, parameter usage scope, validation rules, and validation description.

[0035] Taking the data collection parameter "server address" as an example, the limiting parameters for the server address include: paramID:serverAddr, paramType:String, paramInputType:input, paramRequest:1, paramUnit:other, paramDefault:127.0.0.1, check:^((25[0-5]|2[0-4]\d|[0-9]|1\d{1,2}|[1-9]\d)(\.(25[0-5]|2[0-4]\d|[0-9]|1\d{1,2}|[1-9]\d)){3})$, and checkDescribe:ip v4. Wherein, paramID represents the parameter ID, paramType represents the parameter type, paramInputType represents the parameter input type, paramRequest represents the parameter request, paramUnit represents the parameter unit, paramDefault represents the parameter usage range (default value), check represents the validation rule, and checkDescribe represents the validation description.

[0036] The graphical user interface (GUI) refers to the user interface of an industrial IoT platform. On the GUI, users can click buttons to view the parameter configuration page. This page displays data acquisition parameters, each corresponding to a field. The parameter name is used as the field name, with each parameter serving as the header, such as the server address. The GUI is generated by reading a parameter configuration file, allowing users to adjust the values ​​of each data acquisition parameter.

[0037] The parameter configuration file includes three configuration files, each of which records multiple parameter groups. The three configuration files record a data acquisition parameter respectively. The three configuration files are the acquisition rule configuration file, the channel configuration file, and the protocol configuration file.

[0038] The acquisition rule configuration file records multiple first data acquisition parameters and the corresponding limiting parameters for each first data acquisition; the channel configuration file records multiple second data acquisition parameters and the corresponding limiting parameters for each second data acquisition; and the protocol configuration file records multiple third data acquisition parameters and the corresponding limiting parameters for each third data acquisition.

[0039] In practice, firstly, based on the device model of the device to be connected, the target monitoring items of the device to be connected are determined, and a binding relationship is established between the target monitoring items and the target protocol plugin, that is, a binding relationship is established between the target monitoring items and the data acquisition parameters, so as to complete the configuration of the device detection items for the device to be connected.

[0040] For example, users can open the parameter configuration page, which displays the target monitoring items of the devices to be connected. The target monitoring items can be configured under the corresponding third data acquisition parameters. For example, the third data acquisition parameters include data point names. Temperature and humidity can be configured as two attributes under the "Data Point Name" header in the parameter configuration page.

[0041] In addition, the graphical user interface also displays a plugin management page and a device association page. The plugin management page is used to display a list of protocol plugins to facilitate user management and maintenance of created protocol plugins, while the device association page is used to display the binding relationship between protocol plugins and devices to be connected.

[0042] Step S103: In response to the numerical adjustment operation of the data acquisition parameters, determine the acquisition information of the device to be connected.

[0043] In practice, the default values ​​of the data acquisition parameters are displayed on the graphical user interface. Users can adjust the default values ​​of the data acquisition parameters to adapt to the communication requirements and data monitoring requirements of the devices to be connected.

[0044] For example, if the default server address is 127.0.0.1 and the server address corresponding to the device to be connected is 127.10.1.2, the user can directly modify the server address on the graphical user interface to meet the communication requirements of the device to be connected.

[0045] For example, if the default acquisition response time is 0.1 seconds and the required acquisition response time for the device to be connected is 0.05 seconds, the user can directly modify the acquisition response time on the graphical user interface to meet the data monitoring requirements of the device to be connected.

[0046] In an optional embodiment of this application, after the user adjusts the value of the data collection parameters, the system will verify the adjusted value according to the verification rules.

[0047] For example: In response to a numerical adjustment operation on a target data acquisition parameter, the corresponding verification rule for the target data acquisition parameter is obtained. This verification rule then becomes the verification parameter. The adjusted value of the target data acquisition parameter is used to perform a validity check to determine if it meets the verification rule. For instance, it checks if the adjusted server address matches the regular expression in the verification rule. If the adjusted server address matches the regular expression, the validity check is passed. After passing the validity check, the adjusted value of the data acquisition parameter is saved.

[0048] Step S104: In response to the plug-in run command, run the driver file, obtain monitoring data from the device to be monitored based on the collected information, and provide the monitoring data on the graphical user interface.

[0049] In practice, after the user adjusts the data acquisition parameters and saves the adjusted acquisition information, the industrial IoT platform generates an acquisition information file based on the configured acquisition information and sends the acquisition information file to the acquisition service. The acquisition service automatically loads the corresponding driver file to run the communication driver unit, completes device access, and establishes communication between the device to be monitored and the accessed device. After acquiring the monitoring data from the device to be monitored, the monitoring data is sent to the graphical user interface for display.

[0050] It should be noted that each type of protocol plugin requires the separate development of a driver file and three parameter configuration files during the construction process. The driver file and the three parameter configuration files are then packaged together to obtain a protocol plugin package, which is then uploaded to the industrial IoT platform.

[0051] In one example, before selecting a target protocol plugin from a variety of preset protocol plugins that matches the protocol type of the device to be accessed, the protocol plugin package needs to be parsed to extract data acquisition parameters and driver files.

[0052] For example: Obtain the protocol plugin package of the target protocol plugin, parse the protocol plugin package to obtain the parameter configuration file and driver file respectively. Then, extract the data acquisition parameters from the parameter configuration file, persist the data acquisition parameters of the protocol plugin to display the extracted data acquisition parameters on the graphical user interface, and load the driver file into the runtime environment to generate a callable communication driver unit.

[0053] The Industrial Internet of Things (IIoT) platform comprises a four-layer architecture: the device access layer, the platform service layer, the configuration driver layer, and the user layer. The device access layer supports the lifecycle management, enabling, disabling, and uninstallation of various protocol plugins, and supports hot-swappable plugin management. The platform service layer parses and executes protocol plugin configurations. The configuration driver layer supports the configuration of data acquisition parameters for protocol plugins. The user layer provides a framework to dynamically display the management, configuration, and other business functions of protocol plugins.

[0054] The device monitoring data acquisition method provided in this application embodiment can achieve universal configuration of acquisition data of different devices under the same protocol type through three types of standardized configuration files: channel configuration file, acquisition rule configuration file, and protocol configuration file. That is, different models of devices with the same protocol type only need to adjust the values ​​of data acquisition parameters to complete the adaptation. This not only reduces the amount of manual configuration during the device access process, but also has the advantages of fast access, flexible deployment and easy expansion.

[0055] On the one hand, this application achieves the wildcard configuration of communication protocols and the automatic generation of configuration pages by combining protocol plugins with parameter declarations. After importing the protocol plugin, point tables and interactive interfaces can be automatically generated, reducing manual operation and development workload and greatly improving configuration efficiency.

[0056] On the other hand, this application, through the universality of the protocol plugin, can support the rapid access of multi-protocol devices of different models on the same platform. Compared with the traditional method that requires the separate development of an adapter driver for each protocol, this application only needs to load or switch the corresponding protocol plugin to achieve device access, shortening the access cycle from several days to several hours, and significantly increasing the flexibility of device access.

[0057] Finally, by combining a plug-in protocol management library with parameterized declarations, this application achieves standardized management of protocol definition, configuration, and deployment. Unlike the traditional approach where protocols are deeply coupled and upgrades require modifications to the core code, this application can add, delete, modify, and replace protocol plugins without modifying the system kernel, thereby enhancing the scalability and sustainability of the industrial IoT platform.

[0058] As can be seen, the device monitoring data acquisition method provided in this application can use a unified driver file to meet the access requirements of different devices under the same protocol type when acquiring device monitoring data, and abstract the data in the data monitoring process into parameters so as to meet the requirements of different device models under the same protocol type for different data acquisition parameters. There is no need to build separate protocol plugins for different device models, which improves the scalability of protocol plugins. Compared with the device monitoring data acquisition method in the prior art, it solves the problem of low scalability of protocol plugins.

[0059] Based on the same inventive concept, this application also provides an equipment monitoring data acquisition device corresponding to the equipment monitoring data acquisition method. Since the principle of the device in this application is similar to the equipment monitoring data acquisition method described above, the implementation of the device can refer to the implementation of the method, and the repeated parts will not be described again.

[0060] Please see Figure 2 , Figure 2 This is a schematic diagram of the structure of a device for monitoring data acquisition provided in an embodiment of this application. Figure 2 As shown, the device monitoring data acquisition device 200 includes: The plugin acquisition module 201 is used to select a target protocol plugin that matches the protocol type of the device to be accessed from a variety of preset protocol plugins. Each preset protocol plugin is used as a communication interface plugin for a protocol type. The target protocol plugin includes a parameter configuration file and a driver file corresponding to the protocol type. The parameter configuration file is configured with data acquisition parameters. The parameter display module 202 is used to provide the data acquisition parameters in the parameter configuration file on the graphical user interface; The information determination module 203 is used to determine the acquisition information of the device to be connected in response to the numerical adjustment operation of the data acquisition parameters. The device monitoring module 204 is used to respond to the plug-in running command, run the driver file, obtain monitoring data from the device to be monitored based on the collected information, and provide the monitoring data on the graphical user interface.

[0061] Please see Figure 3 , Figure 3 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 3 As shown, the electronic device 300 includes a processor 310, a memory 320, and a bus 330.

[0062] The memory 320 stores machine-readable instructions executable by the processor 310. When the electronic device 300 is running, the processor 310 and the memory 320 communicate via the bus 330. When the machine-readable instructions are executed by the processor 310, they can perform the operations described above. Figure 1 The steps of the device monitoring data acquisition method in the method embodiment shown are described in detail in the method embodiment, and will not be repeated here.

[0063] This application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, can perform the above-described actions. Figure 1The steps of the device monitoring data acquisition method in the method embodiment shown are described in detail in the method embodiment, and will not be repeated here.

[0064] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0065] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. The apparatus embodiments described above are merely illustrative. For example, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. Furthermore, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Additionally, the shown or discussed mutual couplings, direct couplings, or communication connections may be through some communication interfaces; indirect couplings or communication connections between devices or units may be electrical, mechanical, or other forms.

[0066] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0067] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0068] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a processor-executable, non-volatile, computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0069] Finally, it should be noted that the above-described embodiments are merely specific implementations of this application, used to illustrate the technical solutions of this application, and not to limit them. The scope of protection of this application is not limited thereto. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that any person skilled in the art can still modify or easily conceive of changes to the technical solutions described in the foregoing embodiments, or make equivalent substitutions for some of the technical features, within the scope of the technology disclosed in this application. Such modifications, changes, or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be covered within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for acquiring equipment monitoring data, characterized in that, include: For the device to be connected, a target protocol plugin matching the protocol type of the device to be connected is selected from a variety of preset protocol plugins. Each preset protocol plugin is used as a communication interface plugin for a protocol type. The target protocol plugin includes a parameter configuration file and a driver file corresponding to the protocol type. The driver file is compatible with all devices under the same protocol type. The parameter configuration file is configured with multiple sets of data acquisition parameters with limiting parameters and verification rules. The driver file is used to adapt the device to be connected to an industrial communication protocol of a specific communication protocol type. Provide the data acquisition parameters from the parameter configuration file in the graphical user interface; In response to the numerical adjustment operation of the data acquisition parameters, the preset verification rules corresponding to each data acquisition parameter are invoked to perform legality verification on the adjusted value of the target data acquisition parameter. After the verification is passed, the adjusted value of the data acquisition parameter is saved, and a collection information file adapted to the exclusive communication and monitoring requirements of the device to be connected is generated to determine the collection information of the device to be connected. In response to the plug-in execution command, the driver file is run, monitoring data is obtained from the device to be monitored based on the collected information, and the monitoring data is provided on the graphical user interface; The method further includes: Based on the device model of the device to be connected, determine the target monitoring item corresponding to the device to be connected; Establish a binding relationship between the target monitoring item and the data acquisition parameters to complete the configuration of device monitoring items for the device to be connected.

2. The method according to claim 1, characterized in that, The data acquisition parameters include multiple types, including first data acquisition parameters for setting acquisition rules, second data acquisition parameters for setting data transmission channels, and third data acquisition parameters for setting communication protocols. The first data acquisition parameter is determined based on the device access method and acquisition requirements, the second data acquisition parameter is determined based on network and / or link requirements, and the third data acquisition parameter is determined based on the acquisition fields.

3. The method according to claim 1, characterized in that, Before selecting a target protocol plugin from a variety of preset protocol plugins that matches the protocol type of the device to be accessed, the process also includes: Obtain the protocol plugin package of the target protocol plugin, and parse the protocol plugin package to obtain the parameter configuration file and driver file; Extract the data acquisition parameters from the parameter configuration file and display the data acquisition parameters on the graphical user interface; The driver file is loaded into the runtime environment to generate a callable communication driver unit.

4. The method according to claim 1, characterized in that, The method further includes: The target protocol plugin is updated and upgraded using hot update to automatically load the updated parameter configuration file and driver file.

5. A device for acquiring equipment monitoring data, characterized in that, include: The plugin acquisition module is used to select a target protocol plugin that matches the protocol type of the device to be accessed from a variety of preset protocol plugins. Each preset protocol plugin is used as a communication interface plugin for a protocol type. The target protocol plugin includes a parameter configuration file and a driver file corresponding to the protocol type. The driver file is compatible with all devices under the same protocol type. The parameter configuration file is configured with multiple sets of data acquisition parameters with limiting parameters and verification rules. The parameter display module is used to provide the data acquisition parameters in the parameter configuration file on the graphical user interface; The information determination module is used to respond to the numerical adjustment operation of the data acquisition parameters, call the preset verification rules corresponding to each data acquisition parameter to perform legality verification on the adjusted value of the target data acquisition parameter, save the adjusted value of the data acquisition parameter after the verification is passed, generate a collection information file adapted to the exclusive communication and monitoring needs of the device to be connected, and determine the collection information of the device to be connected. The device monitoring module is used to respond to the plug-in running command, run the driver file, obtain monitoring data from the device to be monitored according to the collected information, and provide the monitoring data on the graphical user interface; The device for monitoring and acquiring data is also used for: Based on the device model of the device to be connected, determine the target monitoring item corresponding to the device to be connected; Establish a binding relationship between the target monitoring item and the data acquisition parameters to complete the configuration of device monitoring items for the device to be connected.

6. An electronic device, characterized in that, include: The device includes a processor, a memory, and a bus. The memory stores machine-readable instructions executable by the processor. When the electronic device is running, the processor communicates with the memory via the bus, and the processor executes the machine-readable instructions to perform the steps of the device monitoring data acquisition method as described in any one of claims 1 to 4.

7. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, which, when executed by a processor, performs the steps of the device monitoring data acquisition method as described in any one of claims 1 to 4.

Images