A manufacturing equipment data acquisition and processing system

Abstract

The present invention discloses a manufacturing equipment data collection and processing system, which relates to the technical field of data processing, including calculating the initial backup coefficient of each sub-data, if the cloud EMS system does not have the backup data of the collector, the collector is marked as a new backup collector, and each sub-data is uploaded in sequence according to the initial backup coefficient; if the cloud EMS system already has the backup information of the collector, the predicted backup completion time is calculated, if the predicted backup completion time is less than the preset backup time, the backup adopts a real-time backup strategy, and the difference data of each sub-data is sorted and uploaded in sequence; if the predicted backup completion time is greater than the preset backup time, the backup adopts a non-real-time backup strategy, and the cloud EMS system is uploaded in sequence according to the non-real-time update coefficient, and the collector backup data is updated. It is more intelligent to determine which data needs to be backed up first, and the overall efficiency of the backup is improved.

Description

Technical Field

[0001] The present invention relates to the technical field of data security protection, and in particular to a manufacturing equipment data collection and processing system. Background Art

[0002] With the advent of the industrial age, smart factories have become an important trend in the development of the manufacturing industry. In smart factories, various sensors, equipment and systems continuously generate a large amount of data, which is essential for optimizing production processes, improving production efficiency and ensuring product quality. However, data collection and backup, as a key link in smart factory data management, cannot be ignored. Frequent security incidents such as data leakage, illegal access, and malicious tampering seriously threaten the interests of enterprises and collectors. At present, there are many data security backup technologies on the market, such as snapshots, data mirroring, RAID, and off-site backup. However, these technologies still have many limitations when dealing with big data backup needs: low backup efficiency. In the face of massive data, traditional backup methods often take too long and are difficult to meet the needs of rapid recovery; large resource consumption. The backup process requires a large amount of storage space and computing resources, which increases the operating costs of enterprises; insufficient flexibility, unable to perform intelligent backup according to the real-time changes and importance of data, resulting in redundant backup data or omission of key data; security needs to be improved, and backup data still has the risk of being stolen or tampered with during storage and transmission.

[0003] In the Chinese invention application with application publication number CN118277164A, a data backup and recovery method and system based on cloud computing is disclosed, including step S1: obtaining allocation parameters of files to be backed up; dividing files to be backed up into write hot data, read hot data and cold data; step S2: obtaining local parameters; backing up write hot data or read hot data locally according to the file size of the files to be backed up; step S3: configuring a non-local server computing platform according to local parameters to back up cold data; creating a snapshot for the files to be backed up; judging whether the files to be backed up are complete; if not, restoring the files to be backed up according to the snapshot to obtain a comparison file; if the data of the files to be backed up are complete, no processing is performed; step S4: summarizing the comparison files and feeding them back to the collector;

[0004] In the above invention application, data is divided into important data (read hot data and write hot data) and cold data according to the frequency of use of data by the collector. The important data (read hot data and write hot data) is backed up to the local server, and the cold data is backed up to the non-local server. According to the data processing rate of the server, the data sending rate of the non-local server is adjusted to improve the user experience of the collector. However, in the actual backup process, when the amount of data to be changed is large and the network speed is slow, some write hot data may undergo multiple changes before being uploaded to the server. At this time, if such data is uploaded first, it will lead to frequent data uploads, causing the data to occupy too many resources during peak hours, while the remaining data has been waiting to be uploaded to the server for backup, resulting in low overall backup efficiency. The occupation of system resources (such as CPU, memory, disk I / O, etc.) will also increase, resulting in a decline in the overall performance of the system and affecting the normal operation of other businesses.

[0005] To this end, the present invention provides a manufacturing equipment data collection and processing system. Summary of the invention

[0006] 1. Technical issues to be resolved

[0007] In view of the shortcomings of the prior art, the present invention provides a manufacturing equipment data collection and processing system. The present invention analyzes the real-time backup status of the collector, marks it as new backup, real-time backup and non-real-time backup, and adopts different backup strategies. It is dynamically adjusted according to the changes in the collector data to adapt to different backup needs. The storage and bandwidth resources of the cloud EMS system can be more effectively utilized, which enables the system to more intelligently decide which data needs to be backed up first and which data can be processed later, thereby improving the overall efficiency of the backup and avoiding occupying too many resources during peak hours, thereby solving the technical problems recorded in the background technology.

[0008] (II) Technical solution

[0009] To achieve the above objectives, the present invention is implemented through the following technical solutions: A manufacturing equipment data collection and processing system, comprising:

[0010] The data collection module divides the data of the collector into sub-data and obtains the data volume of each sub-data , Historical access time and historical change time , calculate the initial backup coefficient of each sub-data If the cloud EMS system does not have backup data for the collector, the collector is marked as a new backup collector and each sub-data is backed up according to the initial backup coefficient. Upload the EMS system backups in the cloud in descending order;

[0011] Data analysis module: if the cloud EMS system already has the backup information of the collector, compare the cloud EMS system backup data with the collector data to obtain the difference data volume of each sub-data , calculate the predicted backup completion time Tt .

[0012] First update module, if the backup completion time is predicted Tt If the backup time is less than the preset backup time, the backup will adopt the real-time backup strategy, based on the difference in data volume of each sub-data and the initial backup factor Calculate the real-time update coefficient for each sub-data , update the difference data of each sub-data according to the real-time update coefficient Upload the data to the cloud EMS system in order from largest to smallest, and update the backup data of the collector;

[0013] The second update module predicts the backup completion time Tt If the backup time is greater than the preset backup time, the backup will adopt a non-real-time backup strategy based on the real-time change time of each sub-data. and real-time change difference data volume , calculate the real-time change coefficient of each sub-data , and calculate the non-real-time update coefficient of each sub-data , based on the non-real-time update coefficient Upload the data in order from largest to smallest to the cloud EMS system to update the collector backup data.

[0014] Furthermore, the collector data is obtained and divided into sub-data according to the data storage directory. The data volume of each sub-data is obtained through database management tools (such as MySQL Workbench, Navicat, etc.) , and use system monitoring tools (such as Nagios, Zabbix, Prometheus, etc.) to obtain the historical access time of each sub-data and historical change time .

[0015] Database management tools (such as MySQL Workbench, Navicat, etc.) are important tools for database administrators and developers when managing and maintaining databases. These tools usually provide a graphical interface to facilitate the collector to create, modify, delete, backup, restore, optimize and monitor databases.

[0016] System monitoring tools (such as Nagios, Zabbix, Prometheus, etc.) System monitoring tools are an indispensable and important part of IT operation and maintenance. They can monitor the performance, health and security of the system in real time, and provide system administrators with necessary data support to ensure the stable operation of the system.

[0017] Further, get the data volume of each sub-data , Historical access time and historical change time , after dimensionless processing, calculate the initial backup coefficient of each sub-data :

[0018]

[0019] in, i Indicates the number of each sub-data, i= 1, 2, ..., k , a Indicates the time sequence number of each access to the same sub-data. a= 1, 2, ..., m , b Indicates the time sequence number of each historical change of the same sub-data. b= 1, 2, ..., n .

[0020] Furthermore, the cloud EMS system checks whether there is a device backup list for the collector. If the cloud EMS system does not have backup data for the collector, the collector is marked as a new backup collector, and each sub-data is backed up according to the initial backup coefficient. Upload the cloud EMS system backup in order from largest to smallest.

[0021] Furthermore, if the cloud EMS system already has the backup information of the collector, use database comparison tools (such as DBeaver, Toad Data Point, etc.) or data comparison software (such as Beyond Compare, WinMerge, etc.) to compare the cloud EMS system backup data with the collector data to obtain the difference data volume of each sub-data. . And use network performance testing tools (such as iperf, PsPing, etc.) to detect the maximum network communication volume of the collector Tx .

[0022] Network performance testing tools (such as iperf, PsPing, etc.) are important tools for evaluating and optimizing network performance. They can help collectors understand key indicators such as network transmission speed, latency, packet loss rate, etc., so as to discover potential network problems and optimize them.

[0023] Furthermore, the difference data volume of each sub-data is obtained and maximum network traffic Tx , calculate the predicted backup completion time Tt :

[0024]

[0025] The corresponding predicted backup completion time Tt The calculation formula is as above.

[0026] Furthermore, if the backup completion time is predicted Tt If the backup time is less than the preset backup time, the backup will adopt the real-time backup strategy to obtain the difference data volume of each sub-data and the initial backup factor , after linear normalization, calculate the real-time update coefficient of each sub-data :

[0027]

[0028] The preset backup time is preset by the collector or uses the default backup time.

[0029] Furthermore, when adopting the real-time backup strategy, the difference data of each sub-data is updated according to the real-time update coefficient Upload the data in order from largest to smallest to the cloud EMS system to update the collector backup data.

[0030] Furthermore, if the backup completion time is predicted Tt If it is greater than the preset backup time, the non-real-time backup strategy is adopted for this backup. The system monitoring tool is used to obtain the real-time change time of each sub-data after the collector starts the backup. and real-time change difference data volume , calculate the real-time change coefficient of each sub-data :

[0031]

[0032] in, c Indicates the time sequence number of each real-time change of the same sub-data. c= 1, 2, ..., w .

[0033] Furthermore, obtain the real-time change coefficient of each sub-data and the initial backup factor , after linear normalization, calculate the non-real-time update coefficient of each sub-data :

[0034]

[0035] When adopting a non-real-time backup strategy, the difference data of each sub-data is updated according to the non-real-time update coefficient Upload the data in order from largest to smallest to the cloud EMS system to update the collector backup data.

[0036] Furthermore, the data uploaded to the cloud EMS system includes general network data and low-power network data; and the cloud EMS system and ERP perform two-way data transmission and communication.

[0037] General network data includes WiFi, 4G, 5G and WAN data. The bus signal is input through the general communication data collector. The general counting collector inputs pulses and level signals and outputs andon and buzzer signals. The general network data input bus signals include CAN, RS232, RS485, ETHERNET, and USB. The general network data input pulses and level signals include the total number of production and manufacturing count pulses, the number of qualified production and manufacturing count pulses, the equipment power supply signal, and the abnormal trigger signal.

[0038] The low-power network data input pulses and level signals are input through the low-power counting collector. The low-power network data input pulses and level signals include the total production quantity counting pulses, the qualified production quantity counting pulses, the equipment power supply signal, and the abnormal trigger signal. The bus signal is input through the low-power communication data collector. The low-power network data input bus signals include CAN, RS232, and RS485.

[0039] (III) Beneficial effects

[0040] The present invention provides a manufacturing equipment data collection and processing system, which has the following beneficial effects:

[0041] 1. Divide the collector data into sub-data and obtain the data volume of each sub-data , Historical access time and historical change time , calculate the initial backup coefficient of each sub-data If the cloud EMS system does not have backup data for the collector, the collector is marked as a new backup collector and each sub-data is backed up according to the initial backup coefficient. Uploading cloud EMS system backups in descending order can identify which data is more critical or active for the collector. This helps prioritize the backup of important or frequently changing data, ensuring the timeliness and integrity of the data. Even if the initial data backup is interrupted, the collector's key data can be safely protected.

[0042] 2. If the cloud EMS system already has the backup information of the collector, compare the cloud EMS system backup data with the collector data to obtain the difference in data volume for each sub-data , calculate the predicted backup completion time Tt , if the backup completion time is predicted Tt If the backup time is less than the preset backup time, the backup will adopt the real-time backup strategy, based on the difference in data volume of each sub-data and the initial backup factor Calculate the real-time update coefficient for each sub-data , update the difference data of each sub-data according to the real-time update coefficient Uploading the data to the cloud EMS system in order from large to small and updating the collector backup data can make more effective use of the storage and bandwidth resources of the cloud EMS system. Important data will be uploaded first, while less important data can be backed up when resources are more abundant to avoid occupying too many resources during peak hours. Dynamic adjustments can be made based on changes in collector data to meet different backup needs.

[0043] 3. Predict backup completion time Tt If the backup time is greater than the preset backup time, the backup will adopt a non-real-time backup strategy based on the real-time change time of each sub-data. and real-time change difference data volume , calculate the real-time change coefficient of each sub-data , and calculate the non-real-time update coefficient of each sub-data , based on the non-real-time update coefficient The data is uploaded to the cloud EMS system in order from large to small, and the collector backup data is updated. This enables the system to more intelligently decide which data needs to be backed up first and which data can be processed later, thereby improving the overall efficiency of the backup. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] Figure 1 The present invention is a structural schematic diagram of a manufacturing equipment data acquisition and processing system. DETAILED DESCRIPTION

[0045] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0046] See also Figure 1 The present invention provides a manufacturing equipment data collection and processing system, comprising:

[0047] The data collection module divides the data of the collector into sub-data and obtains the data volume of each sub-data , Historical access time and historical change time , calculate the initial backup coefficient of each sub-data If the cloud EMS system does not have backup data for the collector, the collector is marked as a new backup collector and each sub-data is backed up according to the initial backup coefficient. Upload the EMS system backups in the cloud in descending order;

[0048] Get the data from the collector and divide it into sub-data according to the data storage directory. Get the data volume of each sub-data through database management tools (such as MySQL Workbench, Navicat, etc.) , and use system monitoring tools (such as Nagios, Zabbix, Prometheus, etc.) to obtain the historical access time of each sub-data and historical change time .

[0049] Database management tools (such as MySQL Workbench, Navicat, etc.) are important tools for database administrators and developers when managing and maintaining databases. These tools usually provide a graphical interface to facilitate the collector to create, modify, delete, backup, restore, optimize and monitor databases.

[0050] System monitoring tools (such as Nagios, Zabbix, Prometheus, etc.) System monitoring tools are an indispensable and important part of IT operation and maintenance. They can monitor the performance, health and security of the system in real time, and provide system administrators with necessary data support to ensure the stable operation of the system.

[0051] Get the amount of data for each sub-data , Historical access time and historical change time , after dimensionless processing, calculate the initial backup coefficient of each sub-data :

[0052]

[0053] in, i Indicates the number of each sub-data, i= 1, 2, ..., k , a Indicates the time sequence number of each access to the same sub-data. a= 1, 2, ...,m , b Indicates the time sequence number of each historical change of the same sub-data. b= 1, 2, ..., n .

[0054] Check whether there is a device backup list for the collector in the cloud EMS system. If there is no backup data for the collector in the cloud EMS system, mark the collector as a new backup collector and set each sub-data according to the initial backup coefficient. Upload the cloud EMS system backup in order from largest to smallest.

[0055] Obtain the data from the collector and divide it into sub-data, and obtain the data volume of each sub-data , Historical access time and historical change time , calculate the initial backup coefficient of each sub-data If the cloud EMS system does not have backup data for the collector, the collector is marked as a new backup collector and each sub-data is backed up according to the initial backup coefficient. Uploading cloud EMS system backups in descending order can identify which data is more critical or active for the collector. This helps prioritize the backup of important or frequently changing data, ensuring the timeliness and integrity of the data. Even if the initial data backup is interrupted, the collector's key data can be safely protected.

[0056] Data analysis module: if the cloud EMS system already has the backup information of the collector, compare the cloud EMS system backup data with the collector data to obtain the difference data volume of each sub-data , calculate the predicted backup completion time Tt .

[0057] If the cloud EMS system already has the backup information of the collector, use database comparison tools (such as DBeaver, ToadData Point, etc.) or data comparison software (such as Beyond Compare, WinMerge, etc.) to compare the cloud EMS system backup data with the collector data to obtain the difference data volume of each sub-data. . And use network performance testing tools (such as iperf, PsPing, etc.) to detect the maximum network communication volume of the collector Tx .

[0058] Network performance testing tools (such as iperf, PsPing, etc.) are important tools for evaluating and optimizing network performance. They can help collectors understand key indicators such as network transmission speed, latency, packet loss rate, etc., so as to discover potential network problems and optimize them.

[0059] Get the difference data volume of each sub-data and maximum network traffic Tx , calculate the predicted backup completion time Tt :

[0060]

[0061] The corresponding predicted backup completion time Tt The calculation formula is as above.

[0062] First update module, if the backup completion time is predicted Tt If the backup time is less than the preset backup time, the backup will adopt the real-time backup strategy, based on the difference in data volume of each sub-data and the initial backup factor Calculate the real-time update coefficient for each sub-data , update the difference data of each sub-data according to the real-time update coefficient Upload the data to the cloud EMS system in order from largest to smallest, and update the backup data of the collector;

[0063] If you want to predict the backup completion time Tt If the backup time is less than the preset backup time, the backup will adopt the real-time backup strategy to obtain the difference data volume of each sub-data and the initial backup factor , after linear normalization, calculate the real-time update coefficient of each sub-data :

[0064]

[0065] The preset backup time is preset by the collector or uses the default backup time.

[0066] When adopting the real-time backup strategy, the difference data of each sub-data is updated according to the real-time update coefficient Upload the data in order from largest to smallest to the cloud EMS system to update the collector backup data.

[0067] Enable monitoring and logging in the backup task to record the difference in data volume during the backup process. and the actual amount of backup data , calculate the proportion of redundant backup data of the collector Because :

[0068]

[0069] Among them, the amount of data difference Refers to the difference between the data stored in the cloud EMS system before the backup starts and the data stored in the cloud EMS system after the backup is completed. The actual backup data volume It refers to the total amount of data transferred from the collector to the cloud EMS system during the backup process.

[0070] If the collector has excess backup data Because More than 1, and the backup completion time is predicted Tt If it is greater than 0.8 preset backup time, adjust the preset backup time so that the current predicted backup completion time Tt If the time is greater than the preset backup time and the non-real-time backup policy conditions are met, the non-real-time backup policy is enabled.

[0071] If the cloud EMS system already has the backup information of the collector, compare the cloud EMS system backup data with the collector data to obtain the difference data volume of each sub-data , calculate the predicted backup completion time Tt , if the backup completion time is predicted Tt If the backup time is less than the preset backup time, the backup will adopt the real-time backup strategy, based on the difference in data volume of each sub-data and the initial backup factor Calculate the real-time update coefficient for each sub-data , update the difference data of each sub-data according to the real-time update coefficient Uploading the data to the cloud EMS system in order from large to small and updating the collector backup data can make more effective use of the storage and bandwidth resources of the cloud EMS system. Important data will be uploaded first, while less important data can be backed up when resources are more abundant to avoid occupying too many resources during peak hours. Dynamic adjustments can be made based on changes in collector data to meet different backup needs.

[0072] The second update module predicts the backup completion time Tt If the backup time is greater than the preset backup time, the backup will adopt a non-real-time backup strategy based on the real-time change time of each sub-data. and real-time change difference data volume , calculate the real-time change coefficient of each sub-data , and calculate the non-real-time update coefficient of each sub-data , based on the non-real-time update coefficient Upload the data in order from largest to smallest to the cloud EMS system to update the collector backup data.

[0073] If you want to predict the backup completion time Tt If it is greater than the preset backup time, the non-real-time backup strategy is adopted for this backup. The system monitoring tool is used to obtain the real-time change time of each sub-data after the collector starts the backup. and real-time change difference data volume , calculate the real-time change coefficient of each sub-data :

[0074]

[0075] in, c Indicates the time sequence number of each real-time change of the same sub-data. c= 1, 2, ..., w .

[0076] Get the real-time change coefficient of each sub-data and the initial backup factor , after linear normalization, calculate the non-real-time update coefficient of each sub-data :

[0077]

[0078] When adopting a non-real-time backup strategy, the difference data of each sub-data is updated according to the non-real-time update coefficient Upload the data in order from largest to smallest to the cloud EMS system to update the collector backup data.

[0079] Predict backup completion time Tt If the backup time is greater than the preset backup time, the backup will adopt a non-real-time backup strategy based on the real-time change time of each sub-data. and real-time change difference data volume , calculate the real-time change coefficient of each sub-data , and calculate the non-real-time update coefficient of each sub-data , based on the non-real-time update coefficient The data is uploaded to the cloud EMS system in order from large to small, and the collector backup data is updated. This enables the system to more intelligently decide which data needs to be backed up first and which data can be processed later, thereby improving the overall efficiency of the backup.

[0080] The data uploaded to the cloud EMS system includes general network data and low-power network data; and the cloud EMS system and ERP conduct two-way data transmission and communication.

[0081] General network data includes WiFi, 4G, 5G and WAN data. The bus signal is input through the general communication data collector. The general counting collector inputs pulses and level signals and outputs andon and buzzer signals. The general network data input bus signals include CAN, RS232, RS485, ETHERNET, and USB. The general network data input pulses and level signals include the total number of production and manufacturing count pulses, the number of qualified production and manufacturing count pulses, the equipment power supply signal, and the abnormal trigger signal.

[0082] The low-power network data input pulses and level signals are input through the low-power counting collector. The low-power network data input pulses and level signals include the total production quantity counting pulses, the qualified production quantity counting pulses, the equipment power supply signal, and the abnormal trigger signal. The bus signal is input through the low-power communication data collector. The low-power network data input bus signals include CAN, RS232, and RS485.

[0083] The above embodiments may be implemented in whole or in part by software, hardware, firmware or any other combination thereof. When implemented using software, the above embodiments may be implemented in whole or in part in the form of a computer program product. A person of ordinary skill in the art may appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein may be implemented in electronic hardware, or in a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution.

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

[0085] The above description is only a specific implementation manner of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application.

Claims

1. A manufacturing equipment data collection and processing system, characterized by: include: The data collection module divides the data of the collector into sub-data and obtains the data volume Ls of each sub-data i , historical access time Fs ia and historical change time Gs ib , calculate the initial backup coefficient Cq of each sub-data i If the cloud EMS system does not have backup data for the collector, the collector is marked as a new backup collector, and each sub-data is backed up according to the initial backup coefficient Cq i Upload the EMS system backups in the cloud in descending order; Get the data size Ls of each sub-data i , historical access time Fs ia and historical change time Gs ib , after dimensionless processing, calculate the initial backup coefficient Cq of each sub-data i : Wherein, i represents the number of each sub-data, i=1, 2, ..., k, a represents the time sequence number of each access to the same sub-data, a=1, 2, ..., m, b represents the time sequence number of each historical change of the same sub-data, b=1, 2, ..., n; Data analysis module: if the cloud EMS system has the backup information of the collector, compare the cloud EMS system backup data with the collector data to obtain the difference data volume Cy of each sub-data i , calculate the predicted backup completion time Tt; Get the difference data volume Cy of each sub-data i and the maximum network traffic Tx, calculate the predicted backup completion time Tt: In the first update module, if the predicted backup completion time Tt is less than the preset backup time, the backup will adopt a real-time backup strategy based on the difference data volume Cy of each sub-data. i and the initial backup coefficient Cq i Calculate the real-time update coefficient Sg for each sub-data i , the difference data of each sub-data is updated according to the real-time update coefficient Sg i Upload the data to the cloud EMS system in order from largest to smallest, and update the backup data of the collector; If the predicted backup completion time Tt is less than the preset backup time, the real-time backup strategy is adopted for this backup to obtain the differential data volume Cy of each sub-data i and the initial backup coefficient Cq i , after linear normalization, calculate the real-time update coefficient Sg of each sub-data i : Sg i =Cy i *Cq i When adopting the real-time backup strategy, the difference data of each sub-data is updated according to the real-time update coefficient Sg i Upload the data to the cloud EMS system in order from largest to smallest, and update the backup data of the collector; The second update module predicts that the backup completion time Tt is greater than the preset backup time, so this backup adopts a non-real-time backup strategy, based on the real-time change time Bs of each sub-data ic and real-time change difference data volume Bc ic , calculate the real-time change coefficient Bx of each sub-data i , and calculate the non-real-time update coefficient Fg for each sub-data i , based on the non-real-time update coefficient Fg i Upload the data to the cloud EMS system in order from largest to smallest, and update the backup data of the collector; Enable the monitoring and logging functions in the backup task, record the difference in data volume Sz and the actual backup data volume Bz in real time during the backup process, and calculate the proportion of redundant backup data Pg of the collector: The difference data volume Sz refers to the difference between the data stored in the cloud EMS system before the backup starts and the data stored in the cloud EMS system after the backup is completed. The actual backup data volume Bz refers to the total amount of data transmitted from the collector to the cloud EMS system during the backup process. If the collector's excess backup data ratio Pg exceeds 1, and the predicted backup completion time Tt is greater than 0.8 of the preset backup time, adjust the preset backup time so that the current predicted backup completion time Tt is greater than the preset backup time, meet the non-real-time backup policy conditions, and start the non-real-time backup policy; If the predicted backup completion time Tt is greater than the preset backup time, the non-real-time backup strategy is adopted for this backup, and the system monitoring tool is used to obtain the real-time change time Bs of each sub-data after the collector starts the backup. ic and real-time change difference data volume Bc ic , calculate the real-time change coefficient Bx of each sub-data i : Wherein, c represents the time sequence number of each real-time change of the same sub-data, c = 1, 2, ..., w; Get the real-time change coefficient Bx of each sub-data i and the initial backup coefficient Cq i After linear normalization, the non-real-time update coefficient Fg of each sub-data is calculated i : Fg i =Bx i *Cq i When adopting the non-real-time backup strategy, the difference data of each sub-data is updated according to the non-real-time update coefficient Fg i Upload the data in order from largest to smallest to the cloud EMS system to update the collector backup data.

2. A manufacturing equipment data collection and processing system according to claim 1, characterized in that: Obtain the collector data and divide it into sub-data according to the data storage directory. Obtain the data volume Ls of each sub-data through the database management tool. i , and use the system monitoring tool to obtain the historical access time Fs of each sub-data ia and historical change time Gs ib .

3. The manufacturing equipment data collection and processing system according to claim 1, characterized in that: Check whether there is a device backup list for the collector in the cloud EMS system. If the cloud EMS system does not have backup data for the collector, the collector is marked as a new backup collector and each sub-data is converted according to the initial backup coefficient Cq i Upload the cloud EMS system backup in order from largest to smallest.

4. A manufacturing equipment data collection and processing system according to claim 3, characterized in that: If the cloud EMS system already has the backup information of the collector, use the database comparison tool to compare the cloud EMS system backup data with the collector data to obtain the difference data volume Cy of each sub-data i And use the network performance test tool to detect the maximum network communication volume Tx of the collector.

5. The manufacturing equipment data collection and processing system according to claim 1, characterized in that: The data uploaded to the cloud EMS system includes general network data and low-power network data, and the cloud EMS system and ERP conduct two-way data transmission and communication; General network data includes WiFi, 4G, 5G and WAN data. The bus signal is input through the general communication data collector. The general counting collector inputs pulses and level signals and outputs andon and buzzer signals. The general network data input bus signals include CAN, RS232, RS485, ETHERNET, and USB. The general network data input pulses and level signals include the total number of production and manufacturing count pulses, the number of qualified production and manufacturing count pulses, the equipment power supply signal, and the abnormal trigger signal. The low-power network data input pulses and level signals are input through the low-power counting collector. The low-power network data input pulses and level signals include the total production quantity counting pulses, the qualified production quantity counting pulses, the equipment power supply signal, and the abnormal trigger signal. The bus signal is input through the low-power communication data collector. The low-power network data input bus signals include CAN, RS232, and RS485.

Images