A method and system for monitoring particulate matter operation data of industrial dust removal equipment

By establishing a standardized data mapping layer and MQTT message transmission in industrial dust removal equipment, the isolation problem between the IoT gateway and the PLC communication network is solved, enabling low-risk IoT transformation and efficient data monitoring, and improving the data reliability and scalability of the equipment.

CN123113652APending Publication Date: 2026-11-17GUANGZHOU LAIN ENVIRONMENTAL PROTECTION TECHNOLOGY CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611358578.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-09-03
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

When adding an IoT gateway to existing industrial dust removal equipment, problems such as mismatch between master and slave roles, station number conflicts, increased communication polling time, difficulty in wiring adjustments, and large amount of program modifications exist, and it is also difficult to achieve remote data transmission.

Method used

By establishing a standardized data mapping layer on the human-machine interface terminal, using an industrial IoT gateway to isolate the PLC communication network, and employing MQTT message transmission, Redis real-time storage, and MySQL historical storage, combined with WebSocket web page push, standardized data processing and real-time monitoring are achieved.

Benefits of technology

It reduces the risk of modifying the original PLC serial communication structure and control program, improves the data reliability and query efficiency of multiple devices, and realizes low-risk IoT transformation and scalability.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123113652A_ABST
    Figure CN123113652A_ABST
Patent Text Reader

Abstract

This invention discloses a method and system for monitoring particulate matter operation data of industrial dust removal equipment. The method includes: low-level data acquisition; data conversion; writing standardized data into a predefined local register address space via a human-machine interface terminal; periodically polling the standard register area through an industrial IoT gateway and assembling it into structured messages; message routing; business processing; real-time caching; persistent storage; and front-end display. The system includes: a particulate matter sensor, a programmable logic controller, a human-machine interface terminal, an industrial IoT gateway, an industrial network communication module, an MQTT message broker server, a back-end data processing server, a Redis real-time database, a MySQL historical database, and a web-based monitoring terminal. Using this invention facilitates low-risk IoT upgrades to operational industrial dust removal equipment monitoring systems. This invention can be widely applied in the field of industrial monitoring technology.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of industrial monitoring technology, and in particular to a method and system for monitoring particulate matter operation data of industrial dust removal equipment. Background Technology

[0002] Industrial electrostatic precipitators, air purification equipment, and related environmental protection equipment are widely used in die casting, machining, food machinery, metal processing, and other industrial settings. To determine the operating status and purification effect of dust removal equipment, it is usually necessary to test the particulate matter concentration at the equipment's air inlet, air outlet, or a designated location within the factory area.

[0003] In existing industrial settings, particulate matter sensors are typically used to detect PM2.5, PM10, or other particulate matter parameters. The analog, digital, or serial communication signals output by the sensors are transmitted to a programmable logic controller (PLC), which performs data conversion, display control, equipment interlocking, or alarm determination.

[0004] However, traditional systems typically rely on on-site display and local control. When enterprises need to manage multiple dust collection devices simultaneously, query historical operating data, compare the purification effects of different devices, or view device status remotely via a webpage, they need to add an IoT gateway, network communication, server database, and web-based monitoring system. Adding an IoT gateway directly to the existing serial bus can lead to issues such as a mismatch between the master and slave roles of the new gateway and existing devices, potential station number conflicts, increased communication polling time, difficulties in wiring adjustments, or significant modifications to the original device's program. Summary of the Invention

[0005] In view of this, in order to solve the technical problem that existing methods for monitoring particulate matter operation data in industrial environments do not isolate the PLC communication network and the IoT gateway, thus causing incompatibility and conflicts when adding a new IoT gateway, the present invention proposes a particulate matter operation data monitoring scheme for industrial dust removal equipment, the method comprising: Low-level data acquisition: Raw monitoring data is acquired using particulate matter sensors. Signal conversion: A programmable logic controller (PLC) reads the raw sensor values, performs range conversion and protocol conversion, and outputs standardized data. Local mapping: Standardized data is written to a predefined local register address space via a human-machine interface terminal. Periodic reporting: The industrial IoT gateway periodically polls the standard register area within the HMI, captures data, and assembles it into structured messages (such as JSON format). Message routing: Structured messages are forwarded via an MQTT broker server and managed hierarchically by enterprise code and device ID. Business processing: The backend service subscribes to the data topic for the corresponding device in MQTT, receives the data, and performs business logic such as cleaning and calculation to obtain processed and valid data. Real-time caching: A Redis in-memory database is used to store the latest status value of each device in key-value pairs for high-speed retrieval. Persistent storage: A MySQL relational database is used to store enterprise information, user accounts, equipment ledgers, historical monitoring records, and alarm events in a table structure. Front-end presentation: Finally, the processed data is presented to the user intuitively in the form of charts, dashboards, etc., through a web monitoring page.

[0006] In some embodiments, the validity of the collected data is determined by a human-machine interface terminal or a programmable logic controller. The validity determination includes at least one of the following: communication status detection: if the sensor returns an error code or the link status is abnormal, it is directly rejected; timeliness detection: if the current timestamp has not changed compared to the previous record, or if the interval since the last successful acquisition has exceeded the maximum allowable interval, it is considered invalid; physical range detection: if the measured value exceeds the nominal range of the sensor, it is excluded; repeatability detection: if the values ​​are completely consistent for a preset number of consecutive times (without any fluctuation), it is determined to be a dead value and invalid; abrupt change detection: if the absolute difference between the current value and the previous sampled value exceeds the set change range threshold, it is considered an abnormal jump and is discarded.

[0007] Applying the above method, this invention also proposes a particulate matter operation data monitoring system for industrial dust removal equipment. The system includes: a particulate matter sensor, a programmable logic controller, a human-machine interface terminal, an industrial Internet of Things gateway, an industrial network communication module, an MQTT message broker server, a backend data processing server, a Redis real-time database, a MySQL historical database, and a web monitoring terminal.

[0008] Based on the above solution, this invention provides a method and system for monitoring particulate matter operation data of industrial dust removal equipment. It isolates the original PLC communication network from the IoT gateway through a human-machine interface terminal, establishes a standardized data mapping layer using the existing human-machine interface terminal of the industrial equipment, and enables the IoT gateway to read unified data addresses via industrial Ethernet. This reduces modifications to the original PLC serial communication structure and control program, facilitating low-risk IoT upgrades to already operational industrial dust removal equipment. This invention does not merely upload particulate matter values; instead, it combines and processes particulate matter data, equipment status, data update time, validity markers, alarm information, and equipment identity information. Furthermore, it integrates MQTT message transmission, Redis real-time storage, MySQL historical storage, batch writing, and WebSocket web page push, improving data reliability, query efficiency, and scalability when monitoring multiple industrial devices in real time. Attached Figure Description

[0009] Figure 1 This is a flowchart of the steps of a method for monitoring particulate matter operation data of industrial dust removal equipment according to the present invention; Figure 2 This is a schematic diagram of the mapping between the PLC register and the standard register of the human-machine interface terminal in this invention; Figure 3 This is a flowchart illustrating the data flow of the industrial IoT gateway reading the human-machine interface terminal according to the present invention. Figure 4 This is a flowchart of the backend server data processing of the present invention; Figure 5 This is a flowchart of the network terminal and data retransmission of the present invention; Figure 6 This is a structural block diagram of the present invention for monitoring particulate matter operation data of industrial dust removal equipment. Detailed Implementation

[0010] Regarding the technical problems mentioned in the background section, directly adding an IoT gateway to an existing serial bus may cause the following issues: First, there may be a mismatch between the master and slave roles of the new IoT gateway and the existing devices. For example, if the existing programmable logic controller (PLC) or touchscreen is already acting as a communication master, and the new gateway also needs to act as a master to read data, communication cannot be completed directly through the original serial bus. Second, the existing serial communication bus may already contain multiple slave devices. Adding a new device may cause station number conflicts, increased communication polling time, difficulties in wiring adjustments, or significant modifications to the original device's program. Third, different models of PLCs may use different register addresses, data types, byte order, and communication protocols. Directly adapting the IoT gateway to different PLCs would increase the workload of on-site configuration and maintenance. Fourth, although the particulate data from the existing devices is already displayed on the human-machine interface terminal, there is no unified data outlet, making it difficult to transmit to a remote server.

[0011] 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. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0012] It should be noted that, for ease of description, only the parts relevant to the invention are shown in the accompanying drawings. Unless otherwise specified, the embodiments and features described herein can be combined with each other.

[0013] It should be understood that the terms "system," "apparatus," "unit," and / or "module" used in this application are a method of distinguishing different components, elements, parts, sections, or assemblies at different levels. However, if other terms can achieve the same purpose, they may be replaced by other expressions.

[0014] Unless the context explicitly indicates an exception, words such as "a," "an," "a kind," and / or "the" do not specifically refer to the singular and may also include the plural. Generally speaking, the terms "comprising" and "including" only indicate the inclusion of explicitly identified steps and elements, which do not constitute an exclusive list; a method or apparatus may also include other steps or elements. An element defined by the phrase "comprising a..." does not exclude the presence of other identical elements in the process, method, product, or apparatus that includes the element.

[0015] Furthermore, flowcharts are used in this application to illustrate the operations performed by the system according to embodiments of this application. It should be understood that the preceding or following operations are not necessarily performed precisely in sequence. Instead, the steps can be processed in reverse order or simultaneously. Additionally, other operations can be added to these processes, or one or more steps can be removed from them.

[0016] Reference Figure 1 This is a schematic flowchart of an optional example of a particulate matter operation data monitoring method for industrial dust removal equipment proposed in this invention. The method can be applied to computer equipment, and the monitoring method proposed in this embodiment may include, but is not limited to, the following steps: Step S1: Data acquisition using a particulate matter sensor; Step S2: Read the raw data through the programmable logic controller and perform conversion; Step S3: Map the converted data to the standard local register area through the human-computer interaction terminal; Step S4: Periodically read the standard register area in the human-machine interaction terminal through the industrial IoT gateway and generate structured data messages; Step S5: Receive structured data messages through the MQTT message broker server and construct a device data topic based on the enterprise identifier and the device unique identifier; The system receives data messages through an MQTT Broker, constructs a device data topic based on the enterprise identifier and the device unique identifier (Device ID), and publishes the structured data message to the corresponding device data topic. The device data topic adopts a hierarchical topic structure, for example: enterprise / {EnterpriseID} / device / {DeviceID} / data.

[0017] Step S6: Subscribe to the device data topic in the MQTT message broker server through the backend data server and perform backend data processing; Step S7: Display the processed data from the backend through the web monitoring terminal.

[0018] In some feasible embodiments, step S1 specifically includes: Particulate matter sensors are installed at designated detection locations such as the air inlet, air outlet, inside the air duct, near the electrical control cabinet, or inside the factory of industrial dust removal equipment.

[0019] The particulate matter sensor can detect at least one of PM2.5 and PM10, and can also simultaneously detect total suspended particulate matter, temperature, humidity, wind speed, air volume, pressure difference, or other parameters related to the operating status of the dust removal equipment.

[0020] The particulate matter sensor sends the detection results to the programmable logic controller via RS485 serial communication, analog signals, digital signals, or other industrial communication methods.

[0021] In some feasible embodiments, step S2 specifically includes: The programmable logic controller reads the raw detection values ​​according to the sensor communication protocol and performs data type conversion, proportional conversion, or unit conversion on the raw detection values.

[0022] For example, the raw PM2.5 value uploaded by the particulate matter sensor is written to the data register D11 of the programmable logic controller, PM10 data is written to the data register D12, air volume data is written to the data register D13, and sensor communication status is written to the data register or status bit D14.

[0023] A combined mapping of particulate matter data with data status information. In addition to monitoring values ​​such as PM2.5 and PM10, it also maps update time, data validity markers, operating status, and alarm codes.

[0024] The above register addresses are merely examples and do not constitute a limitation on the scope of protection of this invention.

[0025] In some feasible embodiments, step S3 specifically includes: The human-machine interface terminal reads particulate matter data and equipment status data from the programmable logic controller and maps them to the standard local register area in the human-machine interface terminal.

[0026] Mapping examples are as follows Figure 2 As shown, specifically: The programmable logic controller D11 corresponds to the human-machine interface terminal LW-100, which is used to store PM2.5 data; The programmable logic controller D12 corresponds to the human-machine interface terminal LW-101, which is used to store PM10 data; The programmable logic controller D13 corresponds to the human-machine interface terminal LW-102, which is used to store air volume data; The programmable logic controller D14 corresponds to the human-machine interface terminal LW-103 and is used to save the sensor communication status. The LW-104 human-computer interaction terminal is used to save data update time; The LW-105 human-computer interaction terminal is used to store data validity markers; The LW-106 human-computer interaction terminal is used to save the device's operating status; The LW-107 human-machine interface terminal is used to store alarm codes.

[0027] The human-computer interaction terminal further maps the aforementioned local registers into standard holding registers that can be read via the Modbus TCP communication protocol.

[0028] This preferred embodiment utilizes an industrial human-machine interface (HMI) terminal to establish a standardized register mapping layer. Particulate data and equipment status data from different PLCs are mapped to a unified HMI terminal register area, which is then read by the IoT gateway. The IoT gateway does not need to be directly integrated into the original PLC serial communication bus, thereby reducing communication role conflicts and the risks associated with modifying existing equipment.

[0029] In some feasible embodiments, PM2.5 data, PM10 data, airflow data, status data, and alarm data are arranged according to consecutive addresses, enabling the industrial IoT gateway to obtain a complete set of device data through one or fewer consecutive register read operations. By establishing a standardized register mapping table in the human-machine interface terminal, different models of programmable logic controllers can provide the same or similar data address structure to the industrial IoT gateway.

[0030] This preferred embodiment constructs a combined mapping between particulate matter data and data status information. In addition to PM2.5 and PM10 monitoring values, it also maps update time, data validity markers, operating status, and alarm codes. Multiple monitoring parameters are arranged sequentially or at predetermined addresses, enabling the gateway to read complete data sets in batches.

[0031] In some feasible embodiments, it also includes: Human-computer interaction terminals or programmable logic controllers determine the validity of the collected data.

[0032] Validity judgments include at least one of the following: Determine if the particulate matter data is within the preset physical range; Yes; Determine if the update time has changed between two consecutive data updates; Yes; Determine if the sensor communication status is normal; Yes; Determine if the data remains unchanged multiple times consecutively; No; Determine whether the change in adjacent sampled data exceeds a preset threshold; No; Check if the current data exceeds the maximum allowed update time; No; The judgment criteria given above are all validity conditions.

[0033] When data meets the validity criteria, the data validity flag is set to valid; when data does not meet the validity criteria, the data validity flag is set to invalid or abnormal.

[0034] When an industrial IoT gateway reads particulate matter data, it also reads the corresponding data validity flag, device status, and update time.

[0035] The backend data processing server determines whether to update real-time webpage data, write to the historical database, and generate exception records based on validity flags.

[0036] In some feasible embodiments, step S4 specifically includes: The industrial IoT gateway acts as a Modbus TCP client, and the human-machine interface terminal acts as a Modbus TCP server.

[0037] The industrial IoT gateway periodically reads the standard register area in the human-machine interface terminal based on the terminal's Internet Protocol address, communication port, device number, and register address.

[0038] The read cycle of the industrial IoT gateway can be set from 1 second to 60 seconds. In one embodiment, the read cycle is 5 seconds.

[0039] The data read by the industrial IoT gateway includes at least one of the following: enterprise identifier, device unique identifier, collection time, PM2.5 data, PM10 data, air volume data, device operating status, data validity marker, and alarm code.

[0040] The industrial IoT gateway encapsulates the data it reads into structured data messages.

[0041] Structured data messages can take the following forms: {“Company Identifier”:“Company Number”,“Equipment Identifier”:“Equipment Number”,“Collection Time”:“Time Value”,“PM2.5”:“Detection Value”,“PM10”:“Detection Value”,“Air Volume”:“Detection Value”,“Operating Status”:“Status Value”,“Validity Mark”:“Valid or Invalid”,“Alarm Code”:“Code Value”,“Message Sequence Number”:“Incrementing Sequence Number”}.

[0042] The data flow direction of this process is referenced. Figure 3 .

[0043] In some feasible implementations, the industrial IoT gateway publishes structured data messages to an MQTT message broker server. MQTT topics are hierarchically configured based on enterprise identity and device unique identifiers, for example: Enterprise / Enterprise ID / Device / Device ID / Real-time Data: Different enterprises and devices use different topic paths, enabling the backend data processing server to distinguish data sources based on enterprise and device. Industrial IoT gateways can send messages using Service Quality Level 0, Service Quality Level 1, or Service Quality Level 2. The preferred Service Quality Level is At Least One Delivery to reduce the risk of data loss due to network fluctuations. Each message includes a message sequence number and collection time. The backend data processing server uses the device's unique identifier and message sequence number to determine if duplicate or missing messages have occurred.

[0044] The above format is only for illustrating the data composition and does not limit the specific data encoding format.

[0045] In some feasible embodiments, step S5 specifically includes:

[0046] The industrial IoT gateway publishes structured data messages to the MQTT message broker server.

[0047] MQTT topics are hierarchically configured based on enterprise identity and device unique identifier, for example: Company / Company ID / Equipment / Equipment ID / Real-time Data Different companies and different devices use different topic paths, enabling the backend data processing server to distinguish data sources based on the company and device.

[0048] Industrial IoT gateways can send messages using Quality of Service (QoS) level 0, QoS level 1, or QoS level 2. The preferred QoS level is at least once delivery, to reduce the risk of data loss due to network fluctuations.

[0049] Each message includes a message sequence number and the collection time. The backend data processing server uses the device's unique identifier and the message sequence number to determine whether a message is duplicated or missing.

[0050] In some feasible embodiments, step S6 specifically includes: The backend data processing server subscribes to the device data topic in the MQTT message broker server.

[0051] After receiving the message, the backend data processing server performs the following steps: Parse the enterprise identifier, device unique identifier, collection time, and monitoring data in the message; determine if the enterprise identifier and device unique identifier exist; determine if the message format is complete; determine the data validity flag; determine if the message is duplicated; write the latest valid data to the Redis real-time database; add historical data to the write queue; write data to the MySQL historical database in batches according to preset time intervals or preset number of data entries; determine if the particulate matter concentration exceeds the alarm threshold. The backend data processing procedure refers to Figure 4 .

[0052] The backend data processing server can be implemented using Python, JavaScript, Java, Go, or other server programs, without being limited to a specific programming language or software framework.

[0053] In some feasible embodiments, Redis real-time data storage is also included, specifically comprising: Redis real-time database primarily stores the current data of each device.

[0054] Each device corresponds to a real-time data record, and the record content includes at least one of the following: device unique identifier, latest PM2.5 data, latest PM10 data, latest air volume data, latest device status, latest alarm status, latest data time, and data validity marker.

[0055] When a webpage needs to display the current status of a device, the backend data processing server prioritizes reading the latest data from the Redis real-time database to avoid frequent queries to the MySQL historical database.

[0056] Redis real-time database can also store a queue of data that has not yet been written to the MySQL historical database in batches.

[0057] In some feasible embodiments, MySQL historical data storage is also included, specifically comprising: The MySQL historical database should include at least the following tables: Enterprise Information Table, used to store enterprise ID, enterprise name, enterprise status, and basic enterprise information; User Information Table, used to store user account, password digest, affiliated enterprise, user permissions, and account status; Equipment Information Table, used to store equipment unique identifier, affiliated enterprise, equipment name, equipment model, installation location, human-machine interface terminal address, gateway number, and equipment status; Monitoring Data Table, used to store equipment unique identifier, collection time, PM2.5 data, PM10 data, air volume data, operating status, validity flag, and alarm status; Alarm Record Table, used to store equipment unique identifier, alarm type, alarm start time, alarm end time, alarm value, and processing status.

[0058] Historical data should be indexed according to the device's unique identifier and the time of collection, rather than creating a separate data table for each device.

[0059] The backend data processing server can write data to the MySQL historical database in batches of 100, 500, or 1000 records, or in batches of 1 minute, 5 minutes, or other time intervals.

[0060] In some feasible embodiments, step S7 specifically includes: After a user logs in, the system displays only devices belonging to that company, based on the user's company affiliation and user permissions.

[0061] The web monitoring terminal establishes a continuous connection with the backend data processing server via WebSocket.

[0062] When the backend data processing server receives new and valid data, it will actively push the data to the corresponding web client.

[0063] The webpage should display at least one of the following: device online or offline status, real-time PM2.5 value, real-time PM10 value, real-time airflow value, particulate matter change curve, device alarm status, historical data query results, and device last update time.

[0064] In some feasible embodiments, contingency handling in case of network outages is also included, specifically including: When an industrial IoT gateway is unable to connect to the MQTT message broker server, it will temporarily store the data to be sent in the gateway's local storage area.

[0065] The data to be sent is arranged according to the collection time and message sequence number.

[0066] After the network is restored, the industrial IoT gateway first sends the historical data that was not uploaded, and then resumes sending real-time data, or alternates between sending historical data and real-time data according to a preset ratio.

[0067] The backend data processing server performs deduplication based on the device's unique identifier, collection time, and message sequence number to prevent duplicate records caused by retransmission after network outages.

[0068] If the gateway used does not have local caching capabilities, temporary storage and retransmission can be accomplished by the data sampling and recording area of ​​the human-computer interaction terminal or an independent edge computing module.

[0069] The data flow during the emergency handling process in the event of a network outage is referenced. Figure 5 .

[0070] In some feasible embodiments, it also includes: When PM2.5, PM10, or other monitoring parameters exceed preset thresholds, the programmable logic controller, human-machine interface terminal, or back-end data processing server generates an alarm status.

[0071] Alarm states include at least: parameter over-limit alarm; sensor communication interruption alarm; data not updated for a long time alarm; gateway offline alarm; equipment shutdown alarm; and abnormal data jump alarm.

[0072] The backend data processing server writes alarm records to the MySQL historical database and pushes alarm information to the web monitoring terminal via WebSocket.

[0073] Based on the overall process of the above method, the present invention also provides a particulate matter operation data monitoring system for industrial dust removal equipment, such as... Figure 6 As shown, it includes a particulate matter sensor, a programmable logic controller, a human-machine interface terminal, an industrial IoT gateway, an industrial network communication module, an MQTT message broker server, a backend data processing server, a Redis real-time database, a MySQL historical database, and a web monitoring terminal.

[0074] The connections between the parts are as follows: The particulate matter sensor communicates with the programmable logic controller (PLC); the PLC communicates with the human-machine interface (HMI) terminal; the HMI terminal connects to the industrial IoT gateway via an industrial Ethernet network; the industrial IoT gateway connects to the MQTT message broker server via a network; the backend data processing server subscribes to MQTT messages; the backend data processing server connects to a Redis real-time database and a MySQL historical database respectively; and the web monitoring terminal connects to the backend data processing server via an application programming interface (API) or WebSocket.

[0075] The system's data transmission path is: Particulate matter sensor → Programmable logic controller → Human-machine interface terminal → Industrial IoT gateway → MQTT message broker server → Backend data processing server → Redis real-time database, MySQL historical database and web monitoring terminal.

[0076] The content of the above method embodiments is applicable to this system embodiment. The specific functions implemented in this system embodiment are the same as those in the above method embodiments, and the beneficial effects achieved are also the same as those achieved in the above method embodiments.

[0077] A particulate matter operation data monitoring device for industrial dust removal equipment: At least one processor; At least one memory for storing at least one program; When the at least one program is executed by the at least one processor, the at least one processor implements a particulate matter operation data monitoring method for industrial dust removal equipment as described above.

[0078] The content of the above method embodiments is applicable to the device embodiments. The specific functions implemented by the device embodiments are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.

[0079] A storage medium storing processor-executable instructions, which, when executed by a processor, are used to implement a particulate matter operation data monitoring method for industrial dust removal equipment as described above.

[0080] The content of the above method embodiments is applicable to this storage medium embodiment. The specific functions implemented in this storage medium embodiment are the same as those in the above method embodiments, and the beneficial effects achieved are also the same as those achieved in the above method embodiments.

[0081] The above is a detailed description of the preferred embodiments of the present invention. However, the present invention is not limited to the embodiments described. Those skilled in the art can make various equivalent modifications or substitutions without departing from the spirit of the present invention. All such equivalent modifications or substitutions are included within the scope defined by the claims of this application.

Claims

1. A method for monitoring particulate matter operation data of industrial dust removal equipment, characterized in that, Includes the following steps: Raw data is obtained by collecting data using a particulate matter sensor; The original data is read by a programmable logic controller and transformed to obtain the transformed data; The converted data is mapped to the standard local register area via a human-computer interaction terminal; The standard register area in the human-machine interface terminal is periodically read through the industrial IoT gateway, and structured data messages are generated. The structured data messages are received through the MQTT message broker server, and a device data topic is constructed based on the enterprise identifier and the device unique identifier. The device data topic in the MQTT message broker server is subscribed to by the backend data server, and backend data processing is performed to obtain the backend processed data; The data processed by the backend is displayed through a web-based monitoring terminal.

2. The method for monitoring particulate matter operation data of industrial dust removal equipment according to claim 1, characterized in that, Also includes: The validity of the original data is determined.

3. The method for monitoring particulate matter operation data of industrial dust removal equipment according to claim 2, characterized in that, The validity determination includes at least one of the following conditions: If the original data is within a preset physical range, then the original data is deemed valid. If the update time of the original data changes between two consecutive updates, then the original data is deemed valid. If the communication status of the particulate matter sensor is normal, then the raw data is considered valid. If the original data remains unchanged for a preset number of consecutive times, then the original data is deemed invalid. If the change in adjacent raw data exceeds a preset threshold, the raw data is deemed invalid. If the original data exceeds the maximum allowed update time, the original data is deemed invalid. If the particulate sensor returns a communication error code, the raw data is deemed invalid.

4. The method for monitoring particulate matter operation data of industrial dust removal equipment according to claim 1, characterized in that, Also includes: Build a Redis real-time database and save the current data for each device; Build a MySQL historical database and save enterprise information, user information, equipment information, monitoring data and alarm records in tabular form.

5. The method for monitoring particulate matter operation data of industrial dust removal equipment according to claim 4, characterized in that, The backend data processing process specifically includes: Parse the enterprise identifier, device unique identifier, collection time, and monitoring data in the subscribed messages; Determine if the enterprise logo and equipment unique identifier exist; Determine if the message format is complete; Determine data validity markers; Determine if a message is duplicated; Write the latest valid data to the Redis real-time database; Write historical data into the MySQL historical database; Determine if the particulate matter concentration exceeds the alarm threshold; If the judgment result does not meet the preset data processing conditions, perform exception handling on the corresponding message and stop the subsequent normal data processing of the corresponding message.

6. The method for monitoring particulate matter operation data of industrial dust removal equipment according to claim 1, characterized in that, The data read by the industrial IoT gateway includes at least one of the following: enterprise identifier, unique device identifier, collection time, PM2.5 data, PM10 data, air volume data, device operating status, data validity marker, and alarm code.

7. The method for monitoring particulate matter operation data of industrial dust removal equipment according to claim 1, characterized in that, Also includes: When the industrial IoT gateway cannot connect to the MQTT message broker server, the industrial IoT gateway will temporarily store the data to be sent in the gateway's local storage area. When the industrial IoT gateway reconnects to the MQTT message broker server, it first sends the data from the period of network outage, and then resumes sending real-time data.

8. The method for monitoring particulate matter operation data of industrial dust removal equipment according to claim 1, characterized in that, Also includes: The backend data processing server performs data deduplication based on the device's unique identifier, collection time, and message sequence number.

9. The method for monitoring particulate matter operation data of industrial dust removal equipment according to claim 1, characterized in that, Also includes: When the monitored parameters exceed the preset threshold, the programmable logic controller, human-machine interface terminal, and back-end data processing server generate an alarm status.

10. A particulate matter operation data monitoring system for industrial dust removal equipment, characterized in that, The particulate matter operation data monitoring method for industrial dust removal equipment as described in any one of claims 1-7 includes, in sequence according to the data flow direction, a particulate matter sensor, a programmable logic controller, a human-machine interface terminal, an industrial Internet of Things gateway, an industrial network communication module, an MQTT message broker server, and a back-end data processing server. The back-end data processing server is also connected to a web page detection terminal, a Redis real-time database, and a MySQL historical database, respectively.