Frequency accumulation data storage method and device, equipment and storage medium

Abstract

The invention is suitable for the technical field of data processing, and provides a frequency accumulation data storage method, device and equipment and a storage medium, first relay protection equipment comprises a mainboard and a daughter board, the mainboard is in communication connection with the daughter board, and the method comprises the steps that when the mainboard obtains frequency data, the mainboard is controlled to send the frequency data to the daughter board; when the daughter board determines that the frequency data is within a preset range, first data is determined according to the frequency data, the daughter board is controlled to send the first data to the mainboard, the preset range comprises a low-frequency range and an over-frequency range, and the first data comprises accumulation time, an accumulation event and an accumulation extreme value; the main board is controlled to update the first data in the first file; and the main board is controlled to send the first file to the daughter board, so that the daughter board backs up the first file. Therefore, loss of data stored in the relay protection equipment can be avoided as far as possible, related problems caused by data loss are avoided, and stable operation of the generator can be ensured.

Description

Technical Field

[0001] This application belongs to the field of generator frequency data protection and data storage technology, and particularly relates to frequency accumulation data storage methods, devices, equipment and storage media. Background Technology

[0002] Low-frequency operation of generators can cause low-frequency resonance in steam turbines, leading to fatigue damage to turbine blades. This irreversible fatigue damage, if accumulated to a certain limit, can result in the fracture of blades and the bonding agents of stationary blades, with serious consequences. Therefore, it is necessary to equip large steam turbines with low-frequency (cumulative) protection functions. In actual field applications, some generators are also equipped with overfrequency (cumulative) protection functions.

[0003] Currently, since both low and high frequencies can damage generator units, generators can be protected by generator relay protection devices for frequency protection. Frequency protection usually requires reliable recording of accumulated frequency data.

[0004] However, during the operation of the protection device, due to factors such as internal malfunctions, there may be problems such as loss of frequency accumulation data. The loss of frequency accumulation data may cause the protection device to fail to operate (i.e., it does not operate when it is supposed to), resulting in unstable generator operation. Summary of the Invention

[0005] This application provides a frequency accumulation data storage method, apparatus, device, and storage medium, which can minimize the loss of data stored in relay protection equipment, avoid related problems caused by data loss, and ensure the stable operation of the generator.

[0006] In a first aspect, embodiments of this application provide a frequency accumulation data storage method, applied to a first relay protection device. The first relay protection device includes a main board and a sub-board, which are communicatively connected. The method includes: When the motherboard acquires frequency data, it controls the motherboard to send frequency data to the daughterboard; when the daughterboard determines that the frequency data is within a preset range, it determines the first data based on the frequency data and controls the daughterboard to send the first data to the motherboard. The preset range includes the low frequency range and the over frequency range. The first data includes the cumulative time, cumulative events, and cumulative positive value; it controls the motherboard to update the first data in the first file; it controls the motherboard to send the first file to the daughterboard so that the daughterboard can back up the first file.

[0007] In one possible implementation of the first aspect, when the daughterboard determines that the frequency data is within a preset range, it determines first data based on the frequency data and controls the daughterboard to send the first data to the motherboard, including: The control subboard determines whether the frequency data belongs to the low frequency range; if the frequency data belongs to the low frequency range, it determines the first data based on the frequency data and controls the subboard to send the first data to the motherboard; wherein, the first data includes low frequency accumulation time, low frequency accumulation event and low frequency accumulation value, and the low frequency accumulation value is the minimum value of the frequency data corresponding to the low frequency accumulation time.

[0008] In one possible implementation of the first aspect, the method further includes: If the frequency data is not in the low frequency range, determine whether the frequency data is in the over-frequency range. If the frequency data is in the over-frequency range, determine the first data based on the frequency data and control the daughter board to send the first data to the motherboard. The first data includes the over-frequency accumulation time, the over-frequency accumulation event, and the over-frequency accumulation value. The over-frequency accumulation value is the maximum value of the frequency data corresponding to the over-frequency accumulation time. If the frequency data is not in the over-frequency range, when the daughter board receives the frequency data again, control the daughter board to determine whether the frequency data is in the low frequency range.

[0009] In one possible implementation of the first aspect, after the control motherboard sends a first file to the daughter board so that the daughter board backs up the first file, the method further includes: The mainboard controls the verification of the first file in the daughter board. The verification is used to determine whether the first file in the daughter board is consistent with the first file in the mainboard. If the verification fails, the mainboard controls the mainboard to send the first file to the daughter board again.

[0010] In one possible implementation of the first aspect, controlling the motherboard to send a first file to the daughter board to enable the daughter board to back up the first file includes: periodically controlling the motherboard to send the first file to the daughter board to enable the daughter board to back up the first file. The method further includes: detecting that a first relay protection device is powered on; controlling the motherboard to read the first file from the daughter board; and, when the time for the motherboard to send the first file to the daughter board arrives, controlling the motherboard to send the first file to the daughter board to enable the daughter board to back up the first file.

[0011] In one possible implementation of the first aspect, the method further includes: The first interface is displayed, which includes the first data in the first file of the sub-board; in response to the deletion operation of the target sub-data in the first data, the target sub-data is deleted to obtain the updated first data, and the updated first data is associated with the target content. The target sub-data includes one or more data in the first data, and the target content includes the deletion time and the data type of the deleted target sub-data; the updated first data is used as the first data, and the execution of the control sub-board to send the first data to the main board is triggered again.

[0012] In one possible implementation of the first aspect, the method further includes: Establish a first link between the first relay protection device and the second relay protection device; through the first link, export the first file in the motherboard to the second relay protection device.

[0013] Secondly, embodiments of this application provide a data storage device, including: The acquisition module is used to control the motherboard to send frequency data to the daughterboard when the motherboard acquires frequency data; The determination module is used to determine first data based on the frequency data when the frequency data is determined by the daughter board, and to control the daughter board to send the first data to the motherboard. The preset range includes the low frequency range and the over frequency range. The first data includes the cumulative time, the cumulative event and the cumulative value. The update module is used to control the motherboard to update the first data in the first file; The backup module is used to control the motherboard to send the first file to the daughterboard so that the daughterboard can back up the first file.

[0014] Thirdly, embodiments of this application provide a relay protection device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the method described in any one of the first aspects above.

[0015] Fourthly, embodiments of this application provide a computer-readable storage medium storing a computer program that, when executed by a processor, implements the method described in any one of the first aspects above.

[0016] Fifthly, embodiments of this application provide a computer program product that, when run on a relay protection device, causes the relay protection device to perform the method described in any one of the first aspects above.

[0017] It is understood that the beneficial effects of the second to fifth aspects mentioned above can be found in the relevant descriptions in the first aspect mentioned above, and will not be repeated here.

[0018] The beneficial effects of the embodiments in this application compared with the prior art are: When the first relay protection device acquires frequency data on the main board, it can control the main board to send frequency data to the sub-board. When the sub-board determines that the frequency data is within a preset range (the preset range includes the low-frequency range and the over-frequency range), it determines the first data based on the frequency data and controls the sub-board to send the first data to the main board. The first data includes accumulated time, accumulated events, and accumulated positive values. Afterward, it can control the main board to update the first data in the first file and control the main board to send the first file to the sub-board so that the sub-board can back up the first file. In this way, the first relay protection device uses the main board to acquire frequency data, the sub-board performs calculations and logical judgments, and sends the data to the main board so that the main board can update the first data in the first file. The main board can also back up the first data to the sub-board, so that the main board and the sub-board can store the same data related to low-frequency operation and / or over-frequency operation. Therefore, even if the main board fails, the sub-board still stores the first file, or even if the sub-board fails, the main board still stores the first file. This can avoid the loss of data related to low-frequency operation and / or over-frequency operation, avoid related problems caused by the loss of the first file, and avoid unstable operation of the generator. Attached Figure Description

[0019] To more clearly illustrate the technical solutions in the embodiments of this application, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0020] Figure 1 This is a schematic diagram of a motherboard and a daughterboard provided in an embodiment of this application; Figure 2 This is a schematic flowchart of a frequency accumulation data storage method provided in an embodiment of this application; Figure 3 This is a schematic diagram of the first data provided in an embodiment of this application; Figure 4 This is a flowchart illustrating a frequency accumulation data storage method provided in another embodiment of this application; Figure 5 This is a flowchart illustrating a frequency accumulation data storage method provided in another embodiment of this application; Figure 6 This is a schematic diagram of the structure of the data storage device provided in the embodiments of this application; Figure 7 This is a schematic diagram of the structure of the relay protection device provided in the embodiments of this application. Detailed Implementation

[0021] In the following description, specific details such as particular system architectures and techniques are set forth for illustrative purposes and not for limitation, in order to provide a thorough understanding of the embodiments of this application. However, those skilled in the art will understand that this application may also be implemented in other embodiments without these specific details. In other instances, detailed descriptions of well-known systems, apparatuses, circuits, and methods have been omitted so as not to obscure the description of this application with unnecessary detail.

[0022] It should be understood that, when used in this application specification and the appended claims, the term "comprising" indicates the presence of the described features, integrals, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or a collection thereof.

[0023] It should also be understood that the term “and / or” as used in this application specification and the appended claims means any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0024] As used in this application specification and the appended claims, the term "if" may be interpreted, depending on the context, as "when," "once," "in response to determination," or "in response to detection." Similarly, the phrase "if determined" or "if detected [the described condition or event]" may be interpreted, depending on the context, as meaning "once determined," "in response to determination," "once detected [the described condition or event]," or "in response to detection [the described condition or event]."

[0025] Furthermore, in the description of this application and the appended claims, the terms "first," "second," "third," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0026] References to "one embodiment" or "some embodiments" as described in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0027] For ease of understanding, the examples provided are for reference only and are related to the concepts in the embodiments of this application.

[0028] 1. Low-frequency operation: refers to the operating state with a frequency lower than the preset value. Its harm lies in the cumulative mechanical resonance, which leads to fatigue damage to the turbine blades.

[0029] 2. Over-frequency operation: refers to the operating state where the frequency is higher than the preset value. Its harm lies in the excessive centrifugal force, which can cause mechanical damage or life loss to rotating parts.

[0030] 3. Hash value: This can be understood as a digital fingerprint. Hash values ​​are unique: any file (or piece of data), after being calculated using a specific mathematical algorithm (such as MD5, SHA-256, etc.), will generate a fixed-length and unique string; this string is the hash value. Hash values ​​are sensitive: even if only a single bit in the original file changes (for example, due to errors during transmission or deliberate tampering), the recalculated hash value will be completely different.

[0031] This application provides a frequency accumulation data storage method, apparatus, device, storage medium, and program product. The method is applicable to various scenarios that require recording data related to the low-frequency or over-frequency operation of generators.

[0032] This frequency accumulation data storage method can be implemented by generator relay protection equipment (also known as generator relay protection device, hereinafter referred to as: relay protection equipment). For example... Figure 1 As shown, the generator relay protection device typically includes a main board and a sub-board. The main board and the sub-board are connected to each other and can send data to each other. Furthermore, the main board and the sub-board are connected to each other via a data bus (such as Ethernet).

[0033] Both the main card and the daughter card are dedicated hardware boards. The main board and daughter board typically include non-volatile memory, so that the stored files will not be lost when the generator's relay protection device loses power. This non-volatile memory can be, for example, an embedded MultiMediaCard (eMMC) or flash memory. This application does not limit the type of non-volatile memory.

[0034] In addition, the files stored in the motherboard and daughterboard can be in text file (TXT) format, and other formats are also possible. This application does not limit the format of the files stored in the motherboard and daughterboard.

[0035] Based on the above description, the frequency accumulation data storage method provided in the embodiments of this application will be described in detail below.

[0036] Please see Figure 2 , Figure 2A schematic flowchart of a frequency accumulation data storage method according to an embodiment of this application is shown. Figure 2 As shown, the frequency accumulation data storage method provided in this application may include: S101. When the motherboard acquires frequency data, control the motherboard to send frequency data to the daughterboard.

[0037] Typically, frequency data refers to the frequency amplitude, which is the instantaneous frequency value of the generator's AC signal, used to represent the generator's instantaneous operating state.

[0038] Frequency data can be represented in Hertz (Hz), such as 50.0Hz, 49.8Hz, and 51.2Hz.

[0039] Frequency data is usually determined based on the generator's voltage or current signal. The motherboard can acquire the generator's voltage or current signal in real time and calculate the frequency data.

[0040] In some embodiments, the motherboard periodically collects frequency data in a first cycle. For example, the aforementioned first cycle can be 250ms, and this application does not limit the specific implementation of the first cycle.

[0041] In addition, there is a communication connection between the motherboard and the daughterboard. Each time the motherboard obtains frequency data, it can send the frequency data to the daughterboard so that the daughterboard can perform relevant processing.

[0042] S102. When the daughterboard determines that the frequency data is within the preset range, it determines the first data based on the frequency data and controls the daughterboard to send the first data to the motherboard. The preset range includes the low frequency range and the over frequency range. The first data includes the cumulative time, the cumulative event, and the cumulative value.

[0043] The low-frequency range is preset and used to filter frequency data in the low-frequency range. For example, the low-frequency range is [47.0, 49.5] Hz. This application does not specifically limit the low-frequency range.

[0044] For example, if the frequency data received by the current daughterboard from the motherboard is 48Hz, then the frequency data is in the low frequency range.

[0045] When the frequency data falls within the low-frequency range, the first data includes the low-frequency accumulation time, the low-frequency accumulation event, and the low-frequency accumulation minimum value. The low-frequency accumulation time is the cumulative time the frequency data remains within the low-frequency range. For example, if the received frequency data is continuously within the low-frequency range for one minute, then the low-frequency accumulation time is one minute. The low-frequency accumulation minimum value is the minimum value of the frequency data corresponding to the low-frequency accumulation time. For example, if the low-frequency accumulation time is one minute, and the minimum frequency data value within that one minute is 47Hz, then the low-frequency accumulation minimum value is 47Hz.

[0046] In some embodiments, when the sub-board determines that the frequency data is in the low-frequency range, the first relay protection device can control the counter to start counting and control the sub-board to convert the counter's count into low-frequency accumulation time.

[0047] The over-frequency range is preset and used to filter frequency data that is in an over-frequency state. For example, the over-frequency range is [50.5, 53.0] Hz. This application does not specifically limit the over-frequency range.

[0048] For example, if the frequency data received by the current daughterboard from the motherboard is 51Hz, then the frequency data is in the over-frequency range.

[0049] When frequency data falls within the over-frequency range, the first set of data includes the over-frequency accumulation time, the over-frequency accumulation event, and the over-frequency accumulation value. The over-frequency accumulation time is the cumulative time the frequency data remains within the over-frequency range. For example, if the received frequency data is within the over-frequency range for 1.5 consecutive minutes, the over-frequency accumulation time is 1.5 minutes. The over-frequency accumulation value is the maximum value of the frequency data corresponding to the over-frequency accumulation time. For example, if the over-frequency accumulation time is 1.5 minutes, and the maximum frequency data value within those 1.5 minutes is 53Hz, then the over-frequency accumulation value is 53Hz.

[0050] In some embodiments, when the sub-board determines that the frequency data is within the over-frequency range, the first relay protection device can control the counter to start counting and control the sub-board to convert the counter's count into over-frequency accumulation time.

[0051] In addition, each time the daughterboard obtains the first data, it can send the first data to the motherboard so that the motherboard can perform further processing.

[0052] When the frequency data falls within the low-frequency range, the cumulative time received by the motherboard is the low-frequency cumulative time. When the frequency data falls within the high-frequency range, the cumulative time received by the motherboard is the high-frequency cumulative time.

[0053] Cumulative events include low-frequency cumulative events and over-frequency cumulative events. When the frequency data falls within the low-frequency range, the cumulative event received by the motherboard is a low-frequency cumulative event. When the frequency data falls within the over-frequency range, the cumulative event received by the motherboard is an over-frequency cumulative event.

[0054] The cumulative active value includes both low-frequency and high-frequency cumulative active values. When the frequency data falls within the low-frequency range, the cumulative active value received by the motherboard is the low-frequency cumulative active value, which is the minimum value of the frequency data corresponding to the low-frequency accumulation time. When the frequency data falls within the high-frequency range, the cumulative active value received by the motherboard is the high-frequency cumulative active value, which is the maximum value of the frequency data corresponding to the high-frequency accumulation time.

[0055] In addition, the first data stores cumulative data rather than instantaneous values. Using cumulative values ​​instead of instantaneous values ​​as protection criteria, and through continuous accumulation of time, it accurately quantifies the total amount of abnormal frequency impacts that the equipment is subjected to. Compared with the traditional protection method that only relies on instantaneous frequency thresholds, it can more reliably reflect the actual damage risk of the equipment and effectively avoid the problems of false triggering due to short-term frequency fluctuations or long-term over-limit missed detection.

[0056] S103, Control the motherboard to update the first data in the first file.

[0057] If the frequency data is within the preset range for the first time as described above, after the daughterboard sends the first data to the motherboard, the motherboard can generate a first file to record the first data, that is, the first cumulative time, cumulative events and cumulative values.

[0058] For example, if the frequency data initially falls within the low-frequency range, after the daughterboard sends the initial low-frequency accumulation time, low-frequency accumulation event, and low-frequency accumulation value to the motherboard, the motherboard can generate a first file recording these information. Subsequently, if the frequency data initially falls within the over-frequency range, after the daughterboard sends the initial over-frequency accumulation time, over-frequency accumulation event, and over-frequency accumulation value to the motherboard, the motherboard can add these information to the first file.

[0059] If the frequency data described above is not within the preset range for the first time, after the daughterboard sends the first data to the motherboard, the motherboard can generate the first file and update the first data in the first file, namely the cumulative time, cumulative events, and cumulative active value.

[0060] If the current frequency data belongs to the low-frequency range, the first data includes the low-frequency cumulative time, low-frequency cumulative events, and low-frequency cumulative value. The first relay protection device can update the low-frequency cumulative time, low-frequency cumulative events, and low-frequency cumulative value in the first file. For example, Figure 3 As shown, the current low-frequency cumulative time is 1 minute, and the low-frequency cumulative time already stored in the motherboard is 0.783 minutes. Therefore, the motherboard can update the low-frequency cumulative time to 1.783 minutes. The current low-frequency cumulative value is 47Hz, so the motherboard can record the current low-frequency cumulative value as 47Hz.

[0061] If the current frequency data falls within the overfrequency range, the first data includes the overfrequency accumulation time, overfrequency accumulation event, and overfrequency accumulation value. The first relay protection device can update the overfrequency accumulation time, overfrequency accumulation event, and overfrequency accumulation value in the first file. For example, Figure 3As shown, the current overclocking accumulation time is 1.5 minutes, and the motherboard has already stored an overclocking accumulation time of 5.110 minutes. Therefore, the motherboard can update the overclocking accumulation time to 6.610 minutes. The current overclocking accumulation value is 53Hz, so the motherboard can record the current overclocking accumulation value as 53Hz.

[0062] S104. Control the main board to send the first file to the daughter board so that the daughter board can back up the first file.

[0063] After updating the first data, the motherboard can not only save the first file, but also send the first file to the daughterboard. After receiving the first file, the daughterboard can store the first file. In this way, the motherboard and the daughterboard can store the same first file.

[0064] In some embodiments, the first file may be in TXT format, or it may be in other formats. This application does not limit the format of the first file.

[0065] Based on this, the first file is in TXT format. This visual file format design makes it easy for on-site maintenance users to view, improving the efficiency of troubleshooting and maintenance.

[0066] In this embodiment, when the first relay protection device acquires frequency data on the main board, it can control the main board to send frequency data to the sub-board. When the sub-board determines that the frequency data is within a preset range (the preset range includes a low-frequency range and an over-frequency range), it determines first data based on the frequency data and controls the sub-board to send the first data to the main board. The first data includes accumulated time, accumulated events, and accumulated value. Afterward, it can control the main board to update the first data in a first file and control the main board to send the first file to the sub-board so that the sub-board can back up the first file. Thus, the first relay protection device uses the main board to acquire frequency data and the sub-board to perform calculations and logic. The logic makes a judgment and sends it to the motherboard so that the motherboard updates the first data in the first file. The motherboard can also back up the first data to the daughterboard. This allows the motherboard and daughterboard to store the same data related to low-frequency operation and / or high-frequency operation. Even if the motherboard fails (or is replaced), the daughterboard still stores the first file, or even if the daughterboard fails (or is replaced), the motherboard still stores the first file. This can prevent the loss of data related to low-frequency operation and / or high-frequency operation, avoid related problems caused by the loss of the first file, ensure the continuity of the cumulative logic, and prevent unstable operation of the generator.

[0067] In addition, the aforementioned judgments and determination of the first data are performed by the sub-board, which can reduce the power consumption of the mainboard and avoid the situation where the mainboard performs all the steps, resulting in high power consumption.

[0068] based on Figure 2As described in the embodiment, after receiving frequency data, the daughterboard can perform relevant calculations and logical judgments to determine whether it needs to report data related to low-frequency operation and / or over-frequency operation from the motherboard.

[0069] Below, in conjunction with Figure 4 This paper details the specific implementation process of the frequency accumulation data storage method of this application.

[0070] Please see Figure 4 , Figure 4 A schematic flowchart of a frequency accumulation data storage method according to an embodiment of this application is shown. Figure 4 As shown, the frequency accumulation data storage method provided in this application includes: S201, Receive frequency data.

[0071] S201 can be found here. Figure 2 The description of S101 in the illustrated embodiment regarding the motherboard sending frequency data to the daughterboard will not be repeated here.

[0072] S202. Determine whether the frequency data belongs to the low frequency range.

[0073] If the frequency data is in the low-frequency range, it indicates that the engine's operating frequency has decreased and the engine is operating at a low frequency. The natural frequency of the turbine blades is close to the low-frequency data, which may cause resonance and lead to fatigue damage to the turbine blades.

[0074] Based on this, when the frequency data is in the low-frequency range, the daughterboard can execute S203 and S204; when the frequency data is not in the low-frequency range, the daughterboard can execute S205.

[0075] S203. Determine the first data based on the frequency data.

[0076] The first data can be found here. Figure 2 The description of the first data in S102 of the illustrated embodiment will not be repeated here.

[0077] S204, Send the first data to the motherboard.

[0078] When the frequency data falls within the low-frequency range, the first data includes low-frequency cumulative time, low-frequency cumulative events, and low-frequency cumulative value.

[0079] The first data point when the frequency data falls within the low-frequency range can be found in [reference needed]. Figure 2 The description of the first data in S102 of the embodiment shown, when the frequency data belongs to the low frequency range, will not be repeated here.

[0080] S205. Determine whether the frequency data falls within the over-frequency range.

[0081] If the frequency data falls within the excessive frequency range, it indicates that the engine's operating frequency has increased, the engine is in an excessive frequency operation state, the engine rotor speed has increased, and mechanical damage may occur.

[0082] Among them, the first data point when the frequency data falls within the over-frequency range can be found in [reference needed]. Figure 2 The description of the first data in S102 of the embodiment shown, when the frequency data belongs to the over-frequency range, will not be repeated here.

[0083] When the frequency data falls within the over-frequency range, the first data sent to the motherboard in S204 includes the over-frequency accumulation time, the over-frequency accumulation event, and the over-frequency accumulation value.

[0084] Based on this, when the frequency data is in the over-frequency range, the sub-board can execute S203 and S204; when the frequency data is not in the over-frequency range, the sub-board can execute S201, that is, wait for the sub-board to receive the frequency data again, and when the sub-board receives the frequency data again, control the sub-board to determine whether the frequency data is in the low-frequency range.

[0085] In this embodiment, the daughterboard can determine whether the received frequency data belongs to the low-frequency range or the high-frequency range. When the frequency data belongs to the low-frequency range, it can send data related to low-frequency operation, namely low-frequency accumulation time, low-frequency accumulation event, and low-frequency accumulation value, to the motherboard. When the frequency data belongs to the high-frequency range, it can send data related to high-frequency operation, namely high-frequency accumulation time, high-frequency accumulation event, and high-frequency accumulation value, to the motherboard. This facilitates the motherboard to record data related to low-frequency operation and / or high-frequency operation and back it up to the daughterboard.

[0086] based on Figure 2 and Figure 3 As described in the embodiment shown, when the first relay protection device is powered on again after a power failure, it can read the data in the daughter board so that the data in the daughter board can be backed up in the motherboard, thus avoiding the situation where some or all of the data in the daughter board is not stored in the motherboard.

[0087] Below, in conjunction with Figure 5 This paper details the specific implementation process of the frequency accumulation data storage method of this application.

[0088] Please see Figure 5 , Figure 5 A schematic flowchart of a frequency accumulation data storage method according to an embodiment of this application is shown. Figure 5 As shown, the frequency accumulation data storage method provided in this application includes: S301, The first relay protection device has been detected to be powered on.

[0089] The first relay protection device being powered on refers to the process of the device being connected to the power supply and entering the working state.

[0090] The first relay protection device may be energized under various circumstances. This application does not limit the timing of energizing the first relay protection device.

[0091] In some embodiments, after the construction, expansion or maintenance of the power system is completed, the first relay protection device needs to be reconnected to the power supply in order to restore its protection function.

[0092] In other embodiments, when the power system is restored after a fault or planned power outage, the first relay protection device is energized along with the primary equipment (such as transformers, lines, etc.).

[0093] S302, controls the mainboard to read the first file in the daughterboard.

[0094] It should be understood that there may be situations where the first relay protection device has determined the first data before the power failure, but has not yet sent it to the main board, or the first data has been determined by the sub-board and sent to the main board, but the main board has not yet received it.

[0095] Therefore, there may be inconsistencies between the data stored on the motherboard and the data stored on the daughterboard. Thus, when the first relay protection device is powered on again, it is necessary to control the motherboard to read the first file in the daughterboard in order to fully back up the first file in the daughterboard.

[0096] Among them, after the first relay protection device is powered on again and controls the main board to read the first file in the sub-board, the first file needs to be parsed.

[0097] Furthermore, the method also includes: in response to triggering a first event, controlling the motherboard to read a first file from the daughterboard. The first event is a deletion event of any one or more data items in the first data of the motherboard's first file.

[0098] It should be understood that there are situations where files on the motherboard are intentionally deleted. For example, when the first relay protection device establishes a link with other electronic devices (such as a personal computer), and the user views the first file in the first relay protection device through other electronic devices, the first relay protection device displays the first file on the motherboard. At this time, there is a possibility that the user may accidentally delete any one or more data in the first data of the first file. In this case, if the motherboard detects the deletion operation of any one or more data in the first data, it can trigger the execution of S302 so that the motherboard can obtain the same first file as the daughterboard.

[0099] S303: Control the mainboard to send the first file to the daughterboard so that the daughterboard can back up the first file.

[0100] The process of the motherboard sending data to the daughter board is performed periodically according to the second cycle. Therefore, after the motherboard reads the first file in the daughter board, it can send the first file to the daughter board when the time comes for the motherboard to send data to the daughter board, so that the daughter board can back up the first file.

[0101] For example, the second cycle is 1 minute, which means that the motherboard sends data to the daughterboard once every 1 minute. If the motherboard powers on at 10:00, the motherboard reads the first file in the daughterboard at 10:00, and 10:01 is the time for the motherboard to send data to the daughterboard. At 10:01, the motherboard can send the first file to the daughterboard.

[0102] It should be noted that if S305-S309 are also being executed when S302 is being executed, then after the motherboard updates the first data in the first file, it can also send the first data and the data in the first file read from the daughter board in S302 as a whole to the daughter board, so that the daughter board can be backed up.

[0103] In addition, if the motherboard fails to send the first data (the frequency data is neither in the low frequency range nor the high frequency range) to the motherboard when the backup time for the motherboard to the daughter board is reached, so that the motherboard can update the first data in the first file, then S303 can be executed directly after the backup time for the motherboard to the daughter board is reached.

[0104] Among them, the other descriptions of S303 are similar to Figure 2 The implementation of S104 in the illustrated embodiment is similar, and will not be described in detail here.

[0105] S304. Control the main board to verify the first file in the daughter board. The verification is used to determine whether the first file in the daughter board is consistent with the first file in the main board.

[0106] After the motherboard sends the first file to the daughterboard, the motherboard can also verify the first file in the daughterboard to confirm that the daughterboard has received the complete first file.

[0107] It should be understood that there may be situations such as the first file in the daughterboard being corrupted or the daughterboard not fully receiving the first file sent by the motherboard, which may cause the first file in the daughterboard to differ from the first file in the motherboard.

[0108] In some embodiments, the motherboard can verify the first file in the daughterboard using a hash value. Specifically, the first file stored in the motherboard corresponds to a hash value, and the first file stored in the daughterboard corresponds to a hash value. Since hash values ​​are unique and sensitive (see the description above), the motherboard can compare the hash values ​​of the first file stored in the motherboard and the first file stored in the daughterboard. If the hash values ​​of the first file stored in the motherboard and the first file stored in the daughterboard are the same, it can be determined that the first file in the daughterboard is consistent with the first file in the motherboard, and the verification passes. Otherwise, it can be determined that the first file in the daughterboard is inconsistent with the first file in the motherboard, and the verification fails.

[0109] If the verification fails, it means that the first file stored on the motherboard is inconsistent with the first file stored on the daughterboard. The motherboard needs to resend the first file to the daughterboard so that the daughterboard can back up the same first file as the motherboard. Based on this, if the verification fails, the first relay protection device can execute S303.

[0110] If the verification passes, it means that the first file stored in the motherboard is consistent with the first file stored in the daughterboard. In other words, the first file stored in the motherboard is the same as the first file stored in the daughterboard. The motherboard does not need to perform any operation and can wait. When the time for the next frequency data acquisition arrives, the frequency data can be acquired. Based on this, if the verification passes, the first relay protection device can execute S305.

[0111] S305 controls the motherboard to obtain frequency data.

[0112] S306 controls the mainboard to send frequency data to the daughterboard.

[0113] Among them, S305 and S306 and Figure 2 The implementation of S101 in the illustrated embodiment is similar, and will not be described in detail here.

[0114] S307. When the frequency data is determined to be within the preset range by the sub-board, the first data is determined based on the frequency data. The preset range includes the low frequency range and the over-frequency range. The first data includes the cumulative time, the cumulative event, and the cumulative value.

[0115] S308, the control subboard sends the first data to the main board.

[0116] Among them, S307 and S308 and Figure 2 The implementation of S102 in the illustrated embodiment is similar, and will not be described in detail here.

[0117] S309, controls the motherboard to update the first data in the first file.

[0118] Among them, S309 and Figure 2The implementation of S103 in the illustrated embodiment is similar, and will not be described in detail here.

[0119] S310. Display the first interface, which includes the first data in the first file of the sub-board.

[0120] Typically, when the first relay protection device displays the data stored in the first relay protection device through the interface, the interface displays the data in the sub-board.

[0121] In some embodiments, the first relay protection device may include a display control, which may be a physical button or a virtual control on the display interface of the first relay protection device. When an operation on the display control is received, the first relay protection device may display a first interface, which may include first data in a first file of the sub-board.

[0122] In other embodiments, the first interface can be the homepage interface of the first relay protection device. When the first relay protection device is running and the screen is on, the homepage interface displayed is the first interface.

[0123] S311. In response to the deletion operation of the target sub-data in the first data, delete the target sub-data, obtain the updated first data, and associate the updated first data with target content. The target sub-data includes one or more data in the first data, and the target content includes the deletion time and the data type of the deleted target sub-data.

[0124] The target sub-data in the first data can receive the deletion operation in various ways. This application does not limit the implementation method of receiving the deletion operation for the target sub-data.

[0125] In some embodiments, the first interface includes a delete control, and the delete operation may include a selection operation on the target sub-data and an operation on the delete control.

[0126] In other embodiments, when a trigger operation (such as a click, double-click, or long-press operation) is received on the target sub-data, a delete control for the target sub-data can be displayed. The delete operation may include the trigger operation on the target sub-data and the operation on the delete control.

[0127] The target sub-data includes one or more data points from the first data, meaning the target sub-data may include cumulative time, cumulative events, and / or cumulative positive values. This application does not limit the number or type of the target sub-data.

[0128] For example, the first data in the current first file includes low-frequency cumulative time, low-frequency cumulative events, and low-frequency cumulative positive values, and the target sub-data includes low-frequency cumulative time.

[0129] For example, the first data in the current first file includes the over-frequency accumulation time, the over-frequency accumulation event, and the over-frequency accumulation value, while the target sub-data includes the over-frequency accumulation value.

[0130] For example, the first data in the current first file includes low-frequency cumulative time, low-frequency cumulative events, low-frequency cumulative positive value, excessive-frequency cumulative time, excessive-frequency cumulative events, and excessive-frequency cumulative positive value, while the target sub-data includes low-frequency cumulative time and excessive-frequency cumulative time.

[0131] The target content includes the deletion time and the data type of the target sub-data to be deleted.

[0132] For example, the target sub-data includes low-frequency cumulative time, and the deletion time is 10:00. The target content includes the deletion time: the deletion time of low-frequency cumulative time is 10:00. The target content also includes the data type of the deleted target sub-data: low-frequency cumulative time.

[0133] For example, the target sub-data includes low-frequency cumulative time and high-frequency cumulative time. The deletion time of low-frequency cumulative time is 10:00, and the deletion time of high-frequency cumulative time is 10:01. The target content includes the deletion time: the deletion time of low-frequency cumulative time is 10:00, and the deletion time of high-frequency cumulative time is 10:01. The target content also includes the data types of the deleted target sub-data: low-frequency cumulative time and high-frequency cumulative time.

[0134] It should be understood that after the daughterboard receives the updated first data, it can also trigger the sending of the first data to the motherboard. The daughterboard then sends the updated first data to the motherboard, and the updated first data is associated with the target content.

[0135] In this embodiment, when the first relay protection device is powered on again after a power outage, it can read the first file in the daughter board to back up the first file on the motherboard, thus preventing the situation where some or all of the data in the daughter board is not stored on the motherboard. Furthermore, after the motherboard sends the first file to the daughter board to back up the first file, the motherboard can also verify the first file in the daughter board, thereby preventing situations such as the first file in the daughter board being corrupted or the daughter board not fully receiving the first file sent by the motherboard. Moreover, if a user triggers the deletion of the first data, the daughter board can update the first file and record content related to the deleted data in the first file, such as the deletion time and type. Afterwards, it can back up the data again to the motherboard, so that when the user views the first file later, they can see the specific storage and deletion status of the data in the first file.

[0136] In addition, there is a situation where the first relay protection device is damaged. In this case, the data stored in the first relay protection device can be exported to the second relay protection device to restore the data in the first relay protection device.

[0137] Based on this, in some embodiments, the method further includes: Establish a first link between the first relay protection device and the second relay protection device; through the first link, export the first file in the motherboard to the second relay protection device.

[0138] The first link can be established in various ways, such as through a data cable, through Bluetooth, or through a wireless network. This application does not limit the method of establishing the first link.

[0139] In some embodiments, after a first link is established between the first relay protection device and the second relay protection device, the second relay protection device can display a second interface, which includes an export control. When an operation on the export control is received, the second relay protection device can export a first file from the motherboard of the first relay protection device to the second relay protection device.

[0140] In this way, even if the first relay protection device fails, the first file in the first relay protection device can still be exported to the backup relay protection device, that is, the second relay protection device. This can completely eliminate the problem of cumulative time reset caused by data loss, thereby avoiding the equipment from being subjected to additional abnormal frequency impacts due to "re-timing". This significantly reduces the risk of damage to primary equipment and provides a solid guarantee for the long-term safe and stable operation of key equipment such as generator sets.

[0141] It should be understood that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0142] Corresponding to the frequency accumulation data storage method described in the above embodiments, Figure 6 A structural block diagram of a data storage device provided in an embodiment of this application is shown. For ease of explanation, only the parts related to the embodiments of this application are shown.

[0143] Reference Figure 6 The device includes: The acquisition module 401 is used to control the motherboard to send frequency data to the daughterboard when the motherboard acquires frequency data; The determination module 402 is used to determine first data based on the frequency data when the frequency data is determined by the daughter board within a preset range, and to control the daughter board to send the first data to the motherboard. The preset range includes the low frequency range and the over frequency range. The first data includes the cumulative time, the cumulative event and the cumulative value. Update module 403 is used to control the motherboard to update the first data in the first file; Backup module 404 is used to control the motherboard to send the first file to the daughterboard so that the daughterboard can back up the first file.

[0144] In some embodiments, the determining module 402 is specifically used for: The control subboard determines whether the frequency data belongs to the low frequency range; if the frequency data belongs to the low frequency range, it determines the first data based on the frequency data and controls the subboard to send the first data to the motherboard; wherein, the first data includes low frequency accumulation time, low frequency accumulation event and low frequency accumulation value, and the low frequency accumulation value is the minimum value of the frequency data corresponding to the low frequency accumulation time.

[0145] In some embodiments, the determining module 402 is specifically used for: If the frequency data is not in the low frequency range, determine whether the frequency data is in the over-frequency range. If the frequency data is in the over-frequency range, determine the first data based on the frequency data and control the daughter board to send the first data to the motherboard. The first data includes the over-frequency accumulation time, the over-frequency accumulation event, and the over-frequency accumulation value. The over-frequency accumulation value is the maximum value of the frequency data corresponding to the over-frequency accumulation time. If the frequency data is not in the over-frequency range, when the daughter board receives the frequency data again, control the daughter board to determine whether the frequency data is in the low frequency range.

[0146] In some embodiments, the backup module 404 is specifically used for: The mainboard controls the verification of the first file in the daughter board. The verification is used to determine whether the first file in the daughter board is consistent with the first file in the mainboard. If the verification fails, the mainboard controls the mainboard to send the first file to the daughter board again.

[0147] In some embodiments, the backup module 404 is specifically used for: The control mechanism for the main board to send a first file to the daughter board, enabling the daughter board to back up the first file, includes: periodically controlling the main board to send the first file to the daughter board, enabling the daughter board to back up the first file; detecting the power-on of a first relay protection device; controlling the main board to read the first file from the daughter board; and when the time arrives for the main board to send the first file to the daughter board, controlling the main board to send the first file to the daughter board, enabling the daughter board to back up the first file.

[0148] In some embodiments, the data storage module further includes a deletion module, which is specifically used for: The first interface is displayed, which includes the first data in the first file of the sub-board; in response to the deletion operation of the target sub-data in the first data, the target sub-data is deleted to obtain the updated first data, and the updated first data is associated with the target content. The target sub-data includes one or more data in the first data, and the target content includes the deletion time and the data type of the deleted target sub-data; the updated first data is used as the first data, and the execution of the control sub-board to send the first data to the main board is triggered again.

[0149] In some embodiments, the data storage module further includes an export module, which is specifically used for: Establish a first link between the first relay protection device and the second relay protection device; through the first link, export the first file in the motherboard to the second relay protection device.

[0150] It should be noted that the information interaction and execution process between the above-mentioned devices / units are based on the same concept as the method embodiments of this application. For details on their specific functions and technical effects, please refer to the method embodiments section, and they will not be repeated here.

[0151] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is merely an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments 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. The integrated unit can be implemented in hardware or as a software functional unit. Furthermore, the specific names of the functional units and modules are only for easy differentiation and are not intended to limit the scope of protection of this application. The specific working process of the units and modules in the above system can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0152] This application also provides a relay protection device, which includes: at least one processor, a memory, and a computer program stored in the memory and executable on the at least one processor. When the processor executes the computer program, it implements the steps in any of the above method embodiments.

[0153] For example, this application also provides a structural schematic diagram of a relay protection device. (See attached diagram.) Figure 7 As shown, the relay protection device 500 includes a processor 501, a memory 502, a communication interface 503, and a bus 504. The processor 501, memory 502, and communication interface 503 communicate via the bus 504, or via wireless transmission or other means. The memory 502 stores instructions, and the processor 501 executes the instructions stored in the memory 502. The memory 502 stores program code 5021, and the processor 501 can call the program code 5021 stored in the memory 502 to execute the CNC machining method in the above embodiment.

[0154] It should be understood that in this application, processor 501 can be a CPU, or it can be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. General-purpose processors can be microprocessors or any conventional processor, etc.

[0155] The memory 502 may include read-only memory and random access memory, and provides instructions and data to the processor 501. The memory 502 may also include non-volatile random access memory. The memory 502 may be volatile memory or non-volatile memory, or may include both. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory may be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0156] In addition to the data bus, the 504 bus may also include a power bus, a control bus, and a status signal bus. However, for clarity, in... Figure 7 The general designated all buses as Bus 504.

[0157] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps described in the various method embodiments above.

[0158] This application provides a computer program product that, when run on a mobile terminal, enables the mobile terminal to implement the steps described in the above-described method embodiments.

[0159] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments of this application can be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. The computer-readable medium can include at least: any entity or device capable of carrying the computer program code to the aforementioned data storage device / relay protection device, a recording medium, a computer memory, a read-only memory (ROM), a random access memory (RAM), an electrical carrier signal, a telecommunication signal, and a software distribution medium. Examples include USB flash drives, portable hard drives, magnetic disks, or optical disks.

[0160] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0161] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0162] In the embodiments provided in this application, it should be understood that the disclosed devices / relay protection equipment and methods can be implemented in other ways. For example, the device / relay protection equipment embodiments described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0163] 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.

[0164] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications 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 included within the protection scope of this application.

Claims

1. A frequency accumulation data storage method, characterized in that, The method, applied to a first relay protection device, comprising a main board and a sub-board, wherein the main board and the sub-board are communicatively connected, includes: When the motherboard acquires frequency data, it controls the motherboard to send the frequency data to the daughterboard. When the sub-board determines that the frequency data is within a preset range, it determines first data based on the frequency data and controls the sub-board to send the first data to the main board. The preset range includes a low-frequency range and an over-frequency range. The first data includes cumulative time, cumulative events, and cumulative positive values. Control the motherboard to update the first data in the first file; The motherboard is controlled to send the first file to the daughterboard, so that the daughterboard backs up the first file.

2. The method as described in claim 1, characterized in that, When the sub-board determines that the frequency data is within a preset range, determining the first data based on the frequency data and controlling the sub-board to send the first data to the main board includes: The control board determines whether the frequency data belongs to the low-frequency range; If the frequency data belongs to the low frequency range, the first data is determined based on the frequency data, and the daughterboard is controlled to send the first data to the motherboard; The first data includes low-frequency cumulative time, low-frequency cumulative events, and low-frequency cumulative value, wherein the low-frequency cumulative value is the minimum value of the frequency data corresponding to the low-frequency cumulative time.

3. The method as described in claim 2, characterized in that, The method further includes: If the frequency data does not belong to the low frequency range, then determine whether the frequency data belongs to the over-frequency range; If the frequency data falls within the overfrequency range, the first data is determined based on the frequency data, and the daughterboard is controlled to send the first data to the motherboard; wherein, the first data includes overfrequency accumulation time, overfrequency accumulation event, and overfrequency accumulation value, and the overfrequency accumulation value is the maximum value of the frequency data corresponding to the overfrequency accumulation time; If the frequency data does not belong to the over-frequency range, when the sub-board receives the frequency data again, it controls the sub-board to determine whether the frequency data belongs to the low-frequency range.

4. The method according to any one of claims 1 to 3, characterized in that, After the method of controlling the motherboard to send the first file to the daughterboard so that the daughterboard backs up the first file, the method further includes: The motherboard is controlled to verify the first file in the daughter board, and the verification is used to determine whether the first file in the daughter board is consistent with the first file in the motherboard. If the verification fails, the motherboard is controlled to send the first file to the daughterboard again.

5. The method as described in claim 4, characterized in that, The step of controlling the motherboard to send the first file to the daughterboard so that the daughterboard can back up the first file includes: The motherboard periodically sends the first file to the daughter board so that the daughter board backs up the first file; The method further includes: The first relay protection device was detected to be powered on; The motherboard is controlled to read the first file from the daughterboard; When the time arrives for the motherboard to send the first file to the daughterboard, the motherboard is controlled to send the first file to the daughterboard so that the daughterboard can back up the first file.

6. The method as described in claim 3 or 5, characterized in that, The method further includes: Display a first interface, which includes the first data in the first file of the sub-board; In response to the deletion operation of target sub-data in the first data, the target sub-data is deleted to obtain updated first data, and target content is associated with the updated first data. The target sub-data includes one or more data in the first data, and the target content includes the deletion time and the data type of the deleted target sub-data. The updated first data is used as the first data, and the process is triggered to send the first data from the daughterboard to the motherboard again.

7. The method as described in claim 1, characterized in that, The method further includes: Establish a first link between the first relay protection device and the second relay protection device; The first file in the motherboard is exported to the second relay protection device via the first link.

8. A data storage device, characterized in that, include: The acquisition module is used to control the motherboard to send the frequency data to the daughterboard when the motherboard acquires the frequency data; The determination module is used to determine first data based on the frequency data when the sub-board determines that the frequency data is within a preset range, and to control the sub-board to send the first data to the main board. The preset range includes a low-frequency range and an over-frequency range. The first data includes cumulative time, cumulative events, and cumulative positive values. The update module is used to control the motherboard to update the first data in the first file; A backup module is used to control the motherboard to send the first file to the daughterboard, so that the daughterboard backs up the first file.

9. A relay protection device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the method as described in any one of claims 1 to 7.

10. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1 to 7.

Images