CN116303481A - Storage method, device, equipment and storage medium for fault wave recording data - Google Patents
Storage method, device, equipment and storage medium for fault wave recording data Download PDFInfo
- Publication number
- CN116303481A CN116303481A CN202310573849.7A CN202310573849A CN116303481A CN 116303481 A CN116303481 A CN 116303481A CN 202310573849 A CN202310573849 A CN 202310573849A CN 116303481 A CN116303481 A CN 116303481A
- Authority
- CN
- China
- Prior art keywords
- index
- fault
- storage area
- data
- memory
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 82
- 230000015654 memory Effects 0.000 claims abstract description 94
- 238000013500 data storage Methods 0.000 claims abstract description 52
- 239000004973 liquid crystal related substance Substances 0.000 claims description 4
- 238000004590 computer program Methods 0.000 claims description 3
- 230000008569 process Effects 0.000 description 18
- 238000004891 communication Methods 0.000 description 14
- 238000010586 diagram Methods 0.000 description 14
- 230000003287 optical effect Effects 0.000 description 5
- 230000006870 function Effects 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 239000007787 solid Substances 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 238000004458 analytical method Methods 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 238000012937 correction Methods 0.000 description 1
- 125000004122 cyclic group Chemical group 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000000638 solvent extraction Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/22—Indexing; Data structures therefor; Storage structures
- G06F16/2228—Indexing structures
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
- G06F16/215—Improving data quality; Data cleansing, e.g. de-duplication, removing invalid entries or correcting typographical errors
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0646—Horizontal data movement in storage systems, i.e. moving data in between storage devices or systems
- G06F3/0652—Erasing, e.g. deleting, data cleaning, moving of data to a wastebasket
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The application relates to the technical field of power systems and discloses a method, a device, equipment and a storage medium for storing fault wave recording data, wherein the method is applied to the fault wave recording equipment, the fault wave recording equipment comprises a memory, the memory comprises a storage space, the storage space comprises an index storage area and a data storage area, and the method comprises the following steps: acquiring fault wave recording marks, wherein the fault wave recording marks correspond to the fault wave recording data one by one; determining index information of fault wave recording data according to the fault wave recording mark; storing index information into an index storage area, wherein the index information corresponds to storage positions of fault recording data one by one; according to the index information, the fault recording data are stored in the data storage area, and the method and the device can provide reliable data guarantee for tracing and positioning the fault problem of the inverter by storing multiple groups of fault recording data in the memory.
Description
Technical Field
The embodiment of the application relates to the technical field of power systems, in particular to a method, a device, equipment and a storage medium for storing fault wave recording data.
Background
A photovoltaic inverter (PV inverter or solar inverter) is an inverter that converts variable dc voltage generated by a Photovoltaic (PV) solar panel into AC with a mains frequency, and common fault causes of the photovoltaic inverter include line short circuit, leakage current fault, overvoltage and undervoltage of a power grid, DCI overcurrent protection, and the like, and these fault problems often cause the inverter to work abnormally and be in a standby state, resulting in economic loss. Although the user can know the direct trigger cause of the abnormal working condition of the inverter from the event record table of the inverter, if the whole fault generating process needs to be traced back and the fault problem needs to be analyzed, the prompt of the fault bit is completely insufficient, and at the moment, the fault waveform, namely the fault wave recording, needs to be recorded.
At present, the existing inverter supports fault wave recording, but has the following defects: only a single sample data can be acquired and is easily covered by the next fault record data, so that the fault problem is difficult to trace.
Disclosure of Invention
The embodiment of the application provides a storage method, a device, equipment and a storage medium for fault recording data, wherein by storing a plurality of groups of fault recording data in a memory, reliable data guarantee can be provided for tracing and positioning of inverter fault problems.
The embodiment of the application provides the following technical scheme:
in a first aspect, an embodiment of the present application provides a method for storing fault record data, which is applied to a fault record device, where the fault record device includes a memory, the memory includes a storage space, the storage space includes an index storage area and a data storage area, and the method for storing fault record data includes:
acquiring fault wave recording marks, wherein the fault wave recording marks correspond to the fault wave recording data one by one;
determining index information of fault wave recording data according to the fault wave recording mark;
storing index information into an index storage area, wherein the index information corresponds to storage positions of fault recording data one by one;
and storing the fault recording data to a data storage area according to the index information.
In some embodiments, storing the index information to the index storage area includes:
dividing the index storage area into a plurality of index intervals according to the number of the groups of fault recording data, wherein each index interval corresponds to one group of fault recording data one by one;
traversing the index interval to judge whether the index storage area is fully written;
if the index storage area is not fully written, the index information is written into the index storage area.
In some embodiments, determining whether the index storage area is full comprises:
judging whether the index storage area is empty or not;
if the index storage area is not empty, judging whether the index interval is the last index interval in the index storage area;
if the index interval is the last index interval in the index storage area, determining that the index storage area is full;
the method further comprises the steps of:
and if the index storage area is fully written, performing an erasing operation on the index storage area.
In some embodiments, the method further comprises:
if the index interval is empty, judging whether the index interval is the first index interval in the index storage area;
if the index section is the first index section in the index storage area, the index information is written from the first index section.
In some embodiments, the memory space further includes an index backup memory area, and erasing the index memory area includes:
after the current index information in the index storage area is written into the index backup storage area, an erasing operation is performed on the index storage area.
In some embodiments, the memory space further comprises a polling linked list comprising a plurality of fault log flags, the method further comprising:
After the fault recording data are stored in the data storage area, a fault recording mark corresponding to the fault recording data in the polling linked list is cleared;
and continuing to poll the linked list to acquire the next fault record mark.
In some embodiments, the fault recording device is connected to the external memory, and after the fault recording data is stored in the data storage area, the method further includes:
according to the index information, all fault recording data in the storage space are derived, and the method specifically comprises the following steps:
acquiring the total group number of fault record data to be exported and the group number of the fault record data exported currently in a storage space;
if the number of the groups of the currently exported fault record data is not equal to the total number of the groups of the fault record data to be exported, continuing exporting the fault record data to an external memory according to the index information;
and if the number of the groups of the fault record data which are exported currently is equal to the total number of the groups of the fault record data to be exported, ending the fault record data export operation.
In a second aspect, an embodiment of the present application provides a storage device for fault recording data, applied to a fault recording device, where the fault recording device includes a memory, the memory includes a storage space, the storage space includes an index storage area and a data storage area, and the device includes:
The device comprises a mark acquisition module, a fault recording module and a fault recording module, wherein the mark acquisition module is used for acquiring fault recording marks, and the fault recording marks correspond to fault recording data one by one;
the index determining module is used for determining index information of the fault wave recording data according to the fault wave recording mark;
the index storage module is used for storing index information into an index storage area, wherein the index information corresponds to the storage positions of the fault recording data one by one;
and the data storage module is used for storing the fault recording data to the data storage area according to the index information.
In a third aspect, an embodiment of the present application provides a fault recording device, including:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein, the liquid crystal display device comprises a liquid crystal display device,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform a method of storing fault log data as in the first aspect.
In a fourth aspect, embodiments of the present application provide a non-volatile computer-readable storage medium storing computer-executable instructions for causing a fault logging device to perform a method for storing fault logging data as in the first aspect.
The beneficial effects of this embodiment of the application are: unlike the prior art, the embodiment of the application provides a method for storing fault record data, which is applied to a fault record device, wherein the fault record device comprises a memory, the memory comprises a storage space, the storage space comprises an index storage area and a data storage area, and the method for storing the fault record data comprises the following steps: acquiring fault wave recording marks, wherein the fault wave recording marks correspond to the fault wave recording data one by one; determining index information of fault wave recording data according to the fault wave recording mark; storing index information into an index storage area, wherein the index information corresponds to storage positions of fault recording data one by one; according to the index information, the fault recording data are stored in the data storage area, and the method and the device can provide reliable data guarantee for tracing and positioning the fault problem of the inverter by storing multiple groups of fault recording data in the memory.
Drawings
One or more embodiments are illustrated by way of example and not limitation in the figures of the accompanying drawings, in which like references indicate similar elements, and in which the figures of the drawings are not to scale, unless expressly stated otherwise.
FIG. 1 is a schematic diagram of an application environment provided by an embodiment of the present application;
fig. 2 is a flow chart of a method for storing fault record data according to an embodiment of the present application;
fig. 3 is a schematic diagram of a refinement flow of step S203 in fig. 2;
fig. 4 is a schematic diagram of a refinement flow of step S2032 in fig. 3;
FIG. 5 is a flowchart illustrating an erasing operation on an index storage area according to an embodiment of the present application;
fig. 6 is a schematic diagram of a refinement flow of step S501 in fig. 5;
fig. 7 is a flowchart of determining whether an index section is an index section in an index storage area according to an embodiment of the present application;
FIG. 8 is a schematic overall flow chart of writing index information into an index storage area according to an embodiment of the present application;
FIG. 9 is a schematic flow chart of clearing fault record marks according to an embodiment of the present application;
FIG. 10 is a schematic overall flow chart of writing fault record data into an index storage area according to a fault record flag according to an embodiment of the present application;
fig. 11 is a schematic flow chart of deriving fault recording data according to an embodiment of the present application;
fig. 12 is a schematic diagram of a refinement flow of step S1101 in fig. 11;
fig. 13 is a schematic structural diagram of a fault recording data storage device according to an embodiment of the present application;
Fig. 14 is a schematic structural diagram of a fault recording device according to an embodiment of the present application.
Reference numerals illustrate:
Detailed Description
For the purposes of making the objects, technical solutions and advantages of the embodiments of the present application more clear, the technical solutions of the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.
In addition, technical features described below in the various embodiments of the present application may be combined with each other as long as they do not conflict with each other.
Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used in the description of the present application in this description is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. The term "and/or" as used in this specification includes any and all combinations of one or more of the associated listed items.
The technical scheme of the application is specifically described below with reference to the accompanying drawings of the specification:
referring to fig. 1, fig. 1 is a schematic diagram of an application environment according to an embodiment of the present application;
as shown in fig. 1, the application environment 100 includes: the fault recorder 10, the inverter 20 and the external memory 30, wherein the fault recorder 10 is in communication connection with the inverter 20 through a network, and the fault recorder 10 is in communication connection with the external memory 30 through a network, wherein the network comprises a wired network and/or a wireless network. It is understood that the network includes wireless networks such as 2G, 3G, 4G, 5G, wireless lan, bluetooth, etc., and may also include wired networks such as serial lines, network lines, etc.
In this embodiment of the present application, the fault recording device 10 is configured to acquire and store multiple sets of fault recording data, so as to perform a restoration analysis on the fault recording according to the fault recording data, and it can be understood that the fault recording device 10 may be an electronic product with a communication networking function, such as a computer, a mobile phone, or the like.
In this embodiment of the present application, the fault recording device 10 includes a controller, where the controller is used as a control core of the fault recording device 10 and is configured to control the fault recording device 10 to obtain a fault recording mark, where the fault recording mark corresponds to the fault recording data one by one; determining index information of the fault wave recording data according to the fault wave recording mark, or controlling the fault wave recording device to store the index information into an index storage area, wherein the index information corresponds to storage positions of the fault wave recording data one by one; and storing the fault recording data into a data storage area according to the index information, or controlling the fault recording equipment to package and block the fault recording data to form an EXCEL file and storing the EXCEL file into an external memory.
In the present embodiments, the controller may be a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), a single-chip, ARM (Acorn RISC Machine) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof. The controller may also be any conventional processor, controller, microcontroller, or state machine. A controller may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP and/or any other such configuration, or one or more of a micro-control unit (Microcontroller Unit, MCU), a Field-programmable gate array (Field-Programmable Gate Array, FPGA), a System on Chip (SoC).
In this embodiment of the present application, the fault recording device 10 includes a communication module, where the communication module is communicatively connected to the inverter 20 and is configured to receive a fault recording flag sent by the inverter when the inverter triggers a fault in an operation process, and in this embodiment of the present application, the communication module may implement communication with the internet or the internet, where the communication module includes, but is not limited to, a WIFI module, a ZigBee module, an nb_iot module, a 4G module, a 5G module, a bluetooth module, and other communication units.
In this embodiment of the present application, the fault recording device 10 further includes a memory, where the memory includes a storage space, and the storage space includes an index storage area and a data storage area, and is configured to determine index information of the fault recording data according to the fault recording flag; storing index information into an index storage area, wherein the index information corresponds to storage positions of fault recording data one by one; according to the index information, the fault recording data is stored in the data storage area, and it is understood that the storage area includes, but is not limited to, a Flash storage area.
In the present embodiment, the inverter 20 is a converter that converts direct current electric energy (battery, accumulator jar) into constant frequency, constant voltage or frequency-modulated voltage-modulated alternating current (typically 220v,50hz sine wave). The inverter comprises an inverter bridge, control logic and a filter circuit, in the embodiment of the application, the inverter is used for sending a fault wave recording sign to a communication module of the fault wave recording device when the inverter triggers a fault in the running process, wherein common fault reasons of the inverter comprise line short circuit, leakage current faults, power grid overvoltage and undervoltage, DCI overcurrent protection and the like, and the inverter comprises, but is not limited to, a centralized inverter, a distributed inverter, a string inverter and a micro inverter.
In this embodiment of the present application, the external memory 30 is configured to store a fault recording data file sent by the fault recording device, where the fault recording data file includes an EXCEL file formed by packaging and partitioning the fault recording data, and the external memory includes, but is not limited to, memories such as a hard disk, a floppy disk, an optical disk, and a usb disk. It is understood that the external memory 30 in the embodiment of the present application further includes a memory module, including but not limited to: FLASH memory, NAND FLASH memory, vertical NAND FLASH memory (VNAND), NOR FLASH memory, resistive Random Access Memory (RRAM), magnetoresistive Random Access Memory (MRAM), ferroelectric Random Access Memory (FRAM), spin transfer torque random access memory (STT-RAM), and the like.
Referring to fig. 2, fig. 2 is a flow chart of a method for storing fault record data according to an embodiment of the present application;
the storage method of the fault record data is applied to the fault record equipment, the fault record equipment comprises a memory, the memory comprises a storage space, the storage space comprises an index storage area and a data storage area, and particularly, an execution main body of the storage method of the fault record data is one or more processors of the fault record equipment.
As shown in fig. 2, the method for storing fault record data includes:
step S201: acquiring a fault wave recording mark;
specifically, the storage space includes an internal polling link table, the polling link table is polled by the fault recording device every fixed time interval to obtain a fault recording mark, wherein the fixed time can be set according to actual needs, for example, the fixed time interval is set to 1 second, the fault recording mark is a communication mark agreed by a controller and a communication module in the fault recording device, and is a byte in a real-time data interaction frame of an inverter, the communication module polls the frame in the polling link table and analyzes the frame fault recording mark, wherein the fault recording mark corresponds to the fault recording data one by one, when the fault recording mark is a number of 0, no fault recording data is indicated, when the fault recording mark is a number of 1, the fault recording data needs to be interacted, and attention is paid to the fact that the inverter includes but is not limited to a photovoltaic inverter.
Step S202: determining index information of fault wave recording data according to the fault wave recording mark;
specifically, after a communication module in the fault wave recording device obtains a fault wave recording mark, fault wave recording data corresponding to the fault wave recording mark is obtained according to the fault wave recording mark, the fault wave recording data is divided into a plurality of groups, wherein one group corresponds to one group serial number (ID), index information of the fault wave recording data is determined, the index information comprises the group serial number, occurrence time of the fault and a CRC check value, wherein the CRC (cyclic redundancy check) is a check code with error detection and correction capability, and in the embodiment of the invention, CRC check is to perform CRC-16 check on a structural member 'fault wave recording group (group)' and 'fault wave recording time (date [6 ])' in a program code, so that the CRC check value is obtained, and the reliability of the information is ensured.
Step S203: storing the index information into an index storage area;
referring to fig. 3, fig. 3 is a schematic diagram of a refinement flow chart of step S203 in fig. 2;
as shown in fig. 3, step S203: storing the index information to an index storage area, comprising:
step S2031: equally dividing an index storage area into a plurality of index sections according to the number of groups of fault wave recording data;
specifically, the index storage area is equally divided into a plurality of index sections according to the number of the groups of the fault recording data, wherein each index section corresponds to one group of the fault recording data one by one, namely, each index section corresponds to one group of serial numbers (IDs) of the fault recording data one by one.
Step S2032: traversing the index interval to judge whether the index storage area is fully written;
referring to fig. 4, fig. 4 is a schematic diagram of a refinement flow chart of step S2032 in fig. 3;
as shown in fig. 4, step S2032: storing the index information to an index storage area, comprising:
step S2321: traversing the index interval;
specifically, the index section is traversed from the bottom of the index storage area to the top of the index storage area to determine whether the index storage area is full.
Step S2322: judging whether the index storage area is empty or not;
specifically, whether the index storage area is empty is determined, that is, whether all the index sections in the index storage area are empty is determined by adopting a global traversal mode, if all the index sections in the index storage area are empty, the index storage area is determined to be empty, and step S2325 is entered; if the index storage area is not empty, the process proceeds to step S2323.
Step S2323: judging whether the index interval is the last index interval in the index storage area or not;
specifically, if the index storage area is not empty, determining whether the index section is the last index section in the index storage area, and if the index section is the last index section in the index storage area, proceeding to step S2324; if the index interval is not the last index interval in the index storage area, returning to step S2321, and continuing to traverse the next index interval.
Step S2324: determining that the index storage area is full;
specifically, if the index section is the last index section in the index storage area, the index storage area is assumed to be equally divided into N index sections, the section serial number of each index section is N, wherein the value range of N is [1, N ], and if the serial number N of the currently traversed index section is equal to N, it is determined that the index storage area is full.
Step S2325: writing the index information into an index storage area;
specifically, if the index storage area is empty, it is indicated that each index section in the index storage area is empty, and at this time, the index information is written into the index storage area sequentially from the first index section in the index storage area.
Step S2033: if the index storage area is not fully written, the index information is written into the index storage area;
specifically, if the index storage area is not fully written, the index storage area indicates that there is a space in the index storage area, and the index information is written into the space in the index storage area.
Step S204: according to the index information, storing fault recording data into a data storage area;
specifically, according to the correspondence between the index information and the fault recording data, the fault recording data is stored in the data storage area, and the photovoltaic inverter is taken as an example, and includes a control chip of the photovoltaic inverter, for example: and a digital signal processor (DigitalSignalProcessor, DSP) including a main processor (main DSP) and a sub processor (sub DSP), the main DSP being responsible for inverter control, the sub DSP being responsible for information interaction, data acquisition, etc., in which the main DSP is generally denoted by the numeral "1" and the sub DSP is denoted by the numeral "2", during the process of storing the fault recording data in the data storage area, the fault recording data in the main DSP is stored first, and then the fault recording data in the sub DSP is stored.
In the embodiment of the present application, the data storage area may be divided into a plurality of sectors, and if 10 sets of fault record data are stored, and each set of fault record data occupies 4 sectors, the fault record data needs to occupy 4 x 10 sectors in the data storage area.
Table 1 below is a fault recording data storage format.
TABLE 1
Wherein, the size of 1 sector is 4KB, each group of fault record data occupies 4 sectors, and as shown in table 1, the size of 1 group of fault record data is 16KB.
Referring to fig. 5 again, fig. 5 is a schematic flow chart of an erasing operation on the index storage area according to the embodiment of the present application;
as shown in fig. 5, the erasing operation on the index storage area includes:
step S501: if the index storage area is fully written, performing an erasing operation on the index storage area;
referring to fig. 6 again, fig. 6 is a schematic diagram of a refinement flow of step S501 in fig. 5;
as shown in fig. 6, step S501: if the index storage area is full, performing an erasing operation on the index storage area, including:
step S5011: after the current index information in the index storage area is written into the index backup storage area, the index storage area is erased;
specifically, the storage space further includes an index backup storage area, where the index storage area and the index backup storage area each monopolize a sector, and are divided into corresponding data blocks according to the number of the groups stored in the fault record, so that the number of times of erasing the index storage area corresponds to the number of times of erasing the data areas, taking 10 groups of fault record data as an example, a sector is divided into 10 data blocks, and the start address of each data block is 0, 409, 818, 1227, 1639, 2045, 2454, 2863, 3272 and 3681.
It can be appreciated that, because the FLASH memory has the advantages of non-volatility of memory data and scalability in a large space, it is preferable to set the memory as the FLASH memory, but there is a drawback in the FLASH memory: the data only has 0 and 1 in the memory, because the FLASH data storage programming can not write 0 into 1 and can only write 1 into 0, this means that the FLASH writing target area is guaranteed to be 0xFF each time the data is filled into the FLASH memory, that is, the erasing operation needs to be executed before writing, and the minimum erasing unit of the FLASH is a sector. As can be seen from the above, each time the index storage area of the index information is erased, there is a short "empty window period", and the index storage area is empty in the "empty window period" period, so that the information corresponding to the fault record data cannot be obtained and the storage position of the fault record data cannot be located, which may cause data loss.
Aiming at the problems, when the index storage area is fully written, the current index information in the index storage area is written into the index backup storage area, which is equivalent to backing up the original index information of the index storage area, so that data loss is prevented, and after the operation of writing the current index information in the index storage area into the index backup storage area is completed, the index storage area is erased, so that the index storage area is updated later.
Table 2 below is the storage format of the index storage area and the index backup storage area.
TABLE 2
In the embodiment of the present application, the index storage area is set for accurately locating the storage position of the fault record data, storing the triggering time of the fault record data, and other information such as the group serial number (ID). Therefore, in order to avoid data loss, a sector needs to be opened up to backup the index data, the sector corresponds to the index storage area, namely, an index backup storage area is set, and data backup operation is performed on the historical index in time when the index storage sector is updated each time, so that the probability of data loss can be reduced, and the integrity and reliability of the data are ensured.
Referring to fig. 7 again, fig. 7 is a flowchart illustrating a process of determining whether an index section is the first index section in the index storage area according to an embodiment of the present application;
as shown in fig. 7, the process of determining whether the index section is the first index section in the index storage area includes:
step S701: if the index interval is empty, judging whether the index interval is the first index interval in the index storage area;
specifically, the index storage area is traversed by adopting a global traversing mode, if the currently traversed index section is empty, whether the index section is the first index section in the index storage area is judged, the index storage area is equally divided into N index sections, the section serial number of each index section is N, wherein the value range of N is [1, N ], when the serial number N of the currently traversed index section is equal to 1, the index section is determined to be the first index section in the index storage area, if the index section is the first index section in the index storage area, the step S702 is entered, and if the index section is not the first index section in the index storage area, the traversing is continued until the index section with the serial number N equal to 1 is found.
Step S702: if the index section is the first index section in the index storage area, writing index information from the first index section;
specifically, if the index section is the first index section in the index storage area, the index information is written from the first index section, that is, from the beginning of the index storage area.
Referring to fig. 8 again, fig. 8 is an overall flowchart of writing index information into an index storage area according to an embodiment of the present application;
as shown in fig. 8, the overall process of writing index information into the index storage area includes:
step S801: equally dividing the index storage area into N index sections, wherein the section serial number is N;
step S802: the index storage area is traversed in units of index sections.
Step S803: judging whether the index interval n is empty or not;
specifically, if the index interval n is empty, step S804 is performed; if the index section n is not empty, the process proceeds to step S805.
Step S804: n=n-1.
Specifically, the index interval sequence number traversed currently is decremented by 1.
Step S805: n= 0?
Specifically, it is determined whether the current index section is the first index section in the index storage area.
If the current index section is the first index section in the index storage area, the step S808 is entered; if the current index section is not the first index section in the index storage area, returning to step S803, and continuing to traverse the next index section;
Step S806: n= N?
Specifically, it is determined whether the current index section is the last index section in the index storage area.
If the current index section is the last index section in the index storage area, the step S807 is entered; if the current index section is not the last index section in the index storage area, the process proceeds to step S811.
Step S807: and writing index information in the index backup storage area.
Step S808: index information is written at the beginning of the index storage area.
Step S809: and performing an erasing operation on the index storage area.
Step S810: index information is written in the index storage area.
Step S811: and writing index information at the blank position of the index interval.
The above method steps in the overall flow chart of writing the index information into the index storage area are described above, and are not described in detail herein.
Referring to fig. 9 again, fig. 9 is a schematic flow chart of clearing fault record marks according to an embodiment of the present application;
as shown in fig. 9, the process of clearing the fault log flag includes:
step S901: after the fault recording data are stored in the data storage area, a fault recording mark corresponding to the fault recording data in the polling linked list is cleared;
Specifically, after the operation of storing all fault recording data into the data storage area is completed, the fault recording mark corresponding to the fault recording data in the polling linked list is cleared, and the fault recording mark is set as a digital "0", and when the fault recording mark is set as a digital "1", the fault recording data needs to be interacted, so that the fault recording mark in the polling linked list is directly set as a digital "0", and the purpose of clearing the fault recording mark is achieved.
Step S902: continuing to poll the polling linked list to acquire a next fault record mark;
specifically, after the fault wave recording device is started, the fault wave recording device continuously performs fault wave recording operation, and when the next time the inverter triggers a fault in the operation process, the fault wave recording device continuously polls the polling linked list to acquire a next fault wave recording mark.
Referring to fig. 10 again, fig. 10 is a schematic overall flow chart of writing fault record data into an index storage area according to a fault record flag according to an embodiment of the present application;
as shown in fig. 10, the overall process of writing fault record data into the index storage area according to the fault record flag includes:
Step S1001: judging whether a fault wave recording mark is received or not;
specifically, if a fault record flag is received, step S1002 is entered; if the fault record flag is not received, the process returns to step S1001, and waits for the fault record flag to appear.
Step S1002: the index information is written into the index storage area.
Step S1003: and writing the fault record data into a data storage area.
Step S1004: clearing a fault wave recording mark;
specifically, after the fault recording data are all written into the data storage area, the fault recording flag corresponding to the fault recording data is cleared, and step S1001 is returned to wait for the occurrence of the next fault recording flag.
The above method steps for writing the fault record data into the overall flow diagram of the index storage area according to the fault record flag are described above, and are not repeated herein.
Referring to fig. 11 again, fig. 11 is a schematic flow chart of deriving fault recording data according to an embodiment of the present application;
as shown in fig. 11, the process of deriving fault log data includes:
step S1101: according to the index information, all fault recording data in the storage space are derived;
referring to fig. 12 again, fig. 12 is a detailed flowchart of step S1101 in fig. 11;
As shown in fig. 12, step S1101: and according to the index information, deriving all fault recording data in the storage space, wherein the fault recording data comprises:
step S1111: acquiring the total group number of fault record data to be exported and the group number of the fault record data exported currently in a storage space;
specifically, the upper computer and the central control screen refer to devices that can directly send a control command to the fault recording device, and the user controls the upper computer or the central control screen to issue instructions for exporting all fault recording data to the fault recording device, after the fault recording device analyzes the export command sent by the upper computer, as the index information of the fault recording data is created in the above steps, the index information of the index data area is traversed, so that the total number of fault recording groups to be exported in the storage space of the current fault recording device and the number of groups of fault recording data to be exported currently can be obtained, and it should be noted that the upper computer includes, but is not limited to, a personal computer (personal computer), a host computer (host computer), and an upper computer (upper computer).
Step S1112: judging whether the number of groups of the currently exported fault recording data is equal to the total number of groups of the fault recording data to be exported;
Specifically, after the total number of groups of fault record data to be exported and the total number of groups of fault record data which are exported currently in the storage space are obtained, judging whether the total number of groups of fault record data which are exported currently is equal to the total number of groups of fault record data to be exported, namely comparing the group serial number of the fault record being exported at the moment with the total number of groups of fault record, for example, assuming that the group serial number of the fault record being exported at the moment is a and the total number of groups of fault record data to be exported is a, and when a is not equal to a, entering step S1113; when a is equal to a, step S1114 is advanced.
Step S1113: continuously exporting fault recording data to an external memory according to the index information;
specifically, if the number of groups of the currently exported fault record data is not equal to the total number of groups of the fault record data to be exported, which indicates that the fault record data is not exported completely, the fault record data is exported to the external memory according to the index information.
It should be noted that, the fault recorder is connected to the external memory, and in the software environment of the embodiment of the present application, a minimal file operating system (FATFS) is required to be provided, and the minimal file operating system (FATFS) is a FAT (File Allocation Table) file system module specifically designed for a small embedded system. FATFS is written in compliance with ANSI C and is completely separated from the disk I/O layer, FATFS supports FAT12/FAT16/FAT32 and multiple storage media, and has independent buffer zones for reading and writing multiple files. The fault recording data to be exported can be packaged and segmented through a minimum file operating system (FATFS), and an EXCEL file is formed and imported into an external memory, wherein the external memory refers to a memory except a computer memory and a CPU cache, and the memory can still store data after power is cut off. Including but not limited to hard disk, floppy disk, optical disk, usb disk, etc.
Step S1114: ending the fault recording data export operation;
specifically, if the number of groups of the currently exported fault record data is equal to the total number of groups of the fault record data to be exported, which indicates that the fault record data is exported completely, the export operation is completed, and then the export operation of the fault record data is ended.
In an embodiment of the present application, a method for storing fault record data is provided, and the method is applied to a fault record device, where the fault record device includes a memory, the memory includes a storage space, the storage space includes an index storage area and a data storage area, and the method includes: acquiring fault wave recording marks, wherein the fault wave recording marks correspond to the fault wave recording data one by one; determining index information of fault wave recording data according to the fault wave recording mark; storing index information into an index storage area, wherein the index information corresponds to storage positions of fault recording data one by one; according to the index information, the fault recording data are stored in the data storage area, and the method and the device can provide reliable data guarantee for tracing and positioning the fault problem of the inverter by storing multiple groups of fault recording data in the memory.
Referring to fig. 13 again, fig. 13 is a schematic structural diagram of a fault recording data storage device according to an embodiment of the present application;
the fault recording device comprises a memory, wherein the memory comprises a storage space, the storage space comprises an index storage area, a data storage area, an index backup storage area and a polling linked list, and the fault recording device is applied to one or more processors of the fault recording device.
As shown in fig. 13, the fault log data storage device 130 includes:
the mark acquisition module 131 is configured to acquire fault wave recording marks, where the fault wave recording marks correspond to the fault wave recording data one by one;
the index determining module 132 is configured to determine index information of the fault record data according to the fault record flag;
the index storage module 133 is configured to store index information into the index storage area, where the index information corresponds to storage locations of the fault recording data one by one;
the data storage module 134 is configured to store the fault recording data to the data storage area according to the index information.
In the embodiment of the present application, the index determining module 132 is further configured to:
After the fault recording data are stored in the data storage area, a fault recording mark corresponding to the fault recording data in the polling linked list is cleared;
the polling linked list continues to be polled to acquire the next fault record flag.
In the embodiment of the present application, the index storage module 133 is specifically configured to:
dividing the index storage area into a plurality of index intervals according to the number of the groups of fault recording data, wherein each index interval corresponds to one group of fault recording data one by one;
traversing the index interval to judge whether the index storage area is fully written;
if the index storage area is not fully written, the index information is written into the index storage area;
judging whether the index storage area is fully written or not, comprising:
judging whether the index storage area is empty or not;
if the index storage area is not empty, judging whether the index interval is the last index interval in the index storage area;
if the index interval is the last index interval in the index storage area, determining that the index storage area is full;
if the index storage area is fully written, performing an erasing operation on the index storage area;
if the index interval is empty, judging whether the index interval is the first index interval in the index storage area;
if the index section is the first index section in the index storage area, writing index information from the first index section;
Performing an erase operation on the index storage area, including:
after the current index information in the index storage area is written into the index backup storage area, an erasing operation is performed on the index storage area.
In the embodiment of the present application, after the fault record data is stored in the data storage area, the data storage module 134 is further configured to:
according to the index information, all fault recording data in the storage space are derived, and the method specifically comprises the following steps:
acquiring the total group number of fault record data to be exported and the group number of the fault record data exported currently in a storage space;
if the number of the groups of the currently exported fault record data is not equal to the total number of the groups of the fault record data to be exported, continuing exporting the fault record data to an external memory according to the index information;
and if the number of the groups of the fault record data which are exported currently is equal to the total number of the groups of the fault record data to be exported, the fault record data are stopped being exported.
In this embodiment of the present application, the storage device for fault record data may also be built by a hardware device, for example, the storage device for fault record data may be built by one or more than two chips, and each chip may work in coordination with each other to complete the storage method for fault record data set forth in each embodiment. For another example, the fault log data storage device may also be built from various types of logic devices, such as general purpose processors, digital Signal Processors (DSPs), application Specific Integrated Circuits (ASICs), field Programmable Gate Arrays (FPGAs), single-chip computers, ARM (Acorn RISC Machine) or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combinations of these components.
The storage device of the fault record data in the embodiment of the application can be a device, and also can be a component, an integrated circuit or a chip in a terminal. The device may be a mobile electronic device or a non-mobile electronic device. By way of example, the mobile electronic device may be a cell phone, tablet computer, notebook computer, palm computer, vehicle-mounted electronic device, wearable device, ultra-mobile personal computer (ultra-mobile personal computer, UMPC), netbook or personal digital assistant (personal digital assistant, PDA), etc., and the non-mobile electronic device may be a server, network attached storage (Network Attached Storage, NAS), personal computer (personal computer, PC), television (TV), teller machine or self-service machine, etc., and the embodiments of the present application are not limited in particular.
The storage device of the fault record data in the embodiment of the present application may be a device with an operating system. The operating system may be an Android operating system, an ios operating system, or other possible operating systems, which are not specifically limited in the embodiments of the present application.
The fault record data storage device provided in this embodiment of the present application can implement each process implemented in fig. 2, and in order to avoid repetition, a detailed description is omitted here.
It should be noted that, the storage device for fault record data may execute the storage method for fault record data provided by the embodiment of the present application, and has the corresponding functional module and beneficial effects of the execution method. For technical details not described in detail in the embodiments of the fault record data storage device, reference may be made to the method for storing fault record data provided in the foregoing embodiments.
In an embodiment of the present application, by providing a storage device for fault log data, the storage device includes: the device comprises a mark acquisition module, a fault recording module and a fault recording module, wherein the mark acquisition module is used for acquiring fault recording marks, and the fault recording marks correspond to fault recording data one by one; the index determining module is used for determining index information of the fault wave recording data according to the fault wave recording mark; the index storage module is used for storing index information into an index storage area, wherein the index information corresponds to the storage positions of the fault recording data one by one; the data storage module is used for storing fault recording data to the data storage area according to the index information, and the data storage module can provide reliable data guarantee for tracing and positioning the fault problem of the inverter by storing multiple groups of fault recording data in the memory.
Referring to fig. 14 again, fig. 14 is a schematic structural diagram of a fault recording device according to an embodiment of the present application;
as shown in fig. 14, the fault logging device 140 includes one or more processors 141 and a memory 142. In fig. 14, a processor 141 is taken as an example.
The processor 141 and the memory 142 may be connected by a bus or otherwise, for example in fig. 14.
According to the method and the device, multiple groups of fault recording data can be stored in the memory, so that reliable data guarantee can be provided for tracing and positioning of the inverter fault problem.
The memory 142, as a non-transitory computer readable storage medium, may be used to store non-transitory software programs, non-transitory computer executable programs, and modules, such as program instructions/modules corresponding to the method for storing fault log data in the embodiments of the present application. Processor 141 may implement the method of storing fault log data in any of the method embodiments described below by running non-transitory software programs, instructions, and modules stored in memory 142. In particular, the memory 142 may include Volatile Memory (VM), such as random access memory (random access memory, RAM); memory 142 may also include non-volatile memory (NVM), such as read-only memory (ROM), flash memory (flash memory), hard disk (HDD) or Solid State Drive (SSD), or other non-transitory solid state storage devices; memory 142 may also include a combination of the types of memory described above.
One or more modules are stored in memory 142 that, when executed by one or more processors 141, perform the method of storing fault log data in any of the method embodiments described above, e.g., performing the steps shown in fig. 2 described above; the functions of the various modules or units of fig. 13 may also be implemented.
In this embodiment of the present application, the fault recording device 140 may further have a wired or wireless network interface, a keyboard, an input/output interface, and other components for implementing the functions of the device, which are not described herein.
The present application also provides a non-transitory computer readable storage medium, such as a memory including program code executable by a processor to perform the method of storing fault log data in the above embodiments. For example, the non-volatile computer readable storage medium may be a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a compact disc Read-Only Memory (CDROM), a magnetic tape, a floppy disk, an optical data storage device, and the like.
Embodiments of the present application also provide a computer program product comprising one or more program codes stored in a non-volatile computer-readable storage medium. The processor of the electronic device reads the program code from the non-volatile computer readable storage medium, and the processor executes the program code to complete the method steps of the method for storing fault record data provided in the above-described embodiments.
It will be appreciated by those of ordinary skill in the art that all or part of the steps of implementing the above embodiments may be implemented by hardware, or may be implemented by program code related hardware, and the program may be stored in a non-volatile computer readable storage medium, where the storage medium may be a read only memory, a magnetic disk or optical disk, etc.
From the above description of embodiments, it will be apparent to those skilled in the art that the embodiments may be implemented by means of software plus a general purpose hardware platform, or may be implemented by hardware. Those skilled in the art will appreciate that all or part of the processes implementing the methods of the above embodiments may be implemented by a computer program for instructing relevant hardware, and the program may be stored in a computer readable storage medium, and the program may include processes of the embodiments of the methods described above when executed. The storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), or the like.
Finally, it should be noted that: the above embodiments are only for illustrating the technical solution of the present application, and are not limiting thereof; the technical features of the above embodiments or in the different embodiments may also be combined under the idea of the present application, the steps may be implemented in any order, and there are many other variations of the different aspects of the present application as described above, which are not provided in details for the sake of brevity; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit of the corresponding technical solutions from the scope of the technical solutions of the embodiments of the present application.
Claims (10)
1. A method of storing fault log data for use with a fault log device, the fault log device comprising a memory, the memory comprising a memory space, the memory space comprising an index storage area and a data storage area, the method comprising:
acquiring fault wave recording marks, wherein the fault wave recording marks correspond to the fault wave recording data one by one;
According to the fault wave recording mark, determining index information of the fault wave recording data;
storing the index information into the index storage area, wherein the index information corresponds to the storage positions of the fault recording data one by one;
and storing the fault recording data to the data storage area according to the index information.
2. The method of claim 1, wherein the storing the index information to the index storage area comprises:
equally dividing the index storage area into a plurality of index intervals according to the number of the groups of the fault recording data, wherein each index interval corresponds to one group of fault recording data one by one;
traversing the index interval to judge whether the index storage area is fully written;
and if the index storage area is not fully written, writing the index information into the index storage area.
3. The method of claim 2, wherein said determining whether the index storage area is full comprises:
judging whether the index storage area is empty or not;
if the index storage area is not empty, judging whether the index interval is the last index interval in the index storage area;
If the index interval is the last index interval in the index storage area, determining that the index storage area is full;
the method further comprises the steps of:
and if the index storage area is fully written, performing an erasing operation on the index storage area.
4. A method according to claim 3, characterized in that the method further comprises:
if the index interval is empty, judging whether the index interval is the first index interval in the index storage area;
and if the index section is the first index section in the index storage area, writing the index information from the first index section.
5. The method of claim 3 or 4, wherein the memory space further comprises an index backup memory area, the erasing the index memory area comprising:
and after the current index information in the index storage area is written into the index backup storage area, performing an erasing operation on the index storage area.
6. The method of any of claims 1-4, wherein the memory space further comprises a poll linked list comprising a plurality of fault log flags, the method further comprising:
If the fault recording data are stored in the data storage area, a fault recording mark corresponding to the fault recording data in the polling linked list is cleared;
and continuing to poll the polling linked list to acquire a next fault record mark.
7. The method of any of claims 1-4, wherein the fault logging device is coupled to an external memory, and wherein after storing the fault logging data to the data storage area, the method further comprises:
according to the index information, all fault recording data in the storage space are derived, and the method specifically comprises the following steps:
acquiring the total group number of fault record data to be exported and the group number of fault record data exported currently in the storage space;
if the number of the groups of the currently exported fault record data is not equal to the total number of the groups of the fault record data to be exported, continuing exporting the fault record data to the external memory according to the index information;
and if the number of the groups of the currently exported fault record data is equal to the total number of the groups of the fault record data to be exported, ending the fault record data export operation.
8. A storage device for fault logging data, characterized in that it is applied to a fault logging device, the fault logging device comprising a memory, the memory comprising a storage space, the storage space comprising an index storage area and a data storage area, the device comprising:
The device comprises a mark acquisition module, a fault recording module and a fault recording module, wherein the mark acquisition module is used for acquiring fault recording marks, and the fault recording marks correspond to the fault recording data one by one;
the index determining module is used for determining index information of the fault recording data according to the fault recording mark;
the index storage module is used for storing the index information into the index storage area, wherein the index information corresponds to the storage positions of the fault recording data one by one;
and the data storage module is used for storing the fault recording data to the data storage area according to the index information.
9. A fault logging device, comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein, the liquid crystal display device comprises a liquid crystal display device,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of storing fault log data as claimed in any one of claims 1 to 7.
10. A computer readable storage medium, wherein a computer program or instructions is stored in the storage medium, which when executed, implements a method of storing fault log data according to any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310573849.7A CN116303481B (en) | 2023-05-22 | 2023-05-22 | Storage method, device, equipment and storage medium for fault wave recording data |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310573849.7A CN116303481B (en) | 2023-05-22 | 2023-05-22 | Storage method, device, equipment and storage medium for fault wave recording data |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN116303481A true CN116303481A (en) | 2023-06-23 |
| CN116303481B CN116303481B (en) | 2023-09-12 |
Family
ID=86801778
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310573849.7A Active CN116303481B (en) | 2023-05-22 | 2023-05-22 | Storage method, device, equipment and storage medium for fault wave recording data |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116303481B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116578248A (en) * | 2023-07-12 | 2023-08-11 | 上海泰矽微电子有限公司 | Data processing method, apparatus, and computer readable storage medium |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2002150711A (en) * | 2001-08-29 | 2002-05-24 | Toshiba Corp | Information recording/reproducing device and its method |
| US20020162014A1 (en) * | 2001-02-23 | 2002-10-31 | Power Measurement, Ltd. | Intelligent electronic device with assured data storage on powerdown |
| CN101751389A (en) * | 2008-12-18 | 2010-06-23 | 浙江省电力公司 | Steady state data search method for transformer |
| CN107819328A (en) * | 2017-09-27 | 2018-03-20 | 国家电网公司 | A kind of storage method and device of electric network fault data |
| CN109633331A (en) * | 2018-12-27 | 2019-04-16 | 中国南方电网有限责任公司 | A kind of date storage method and fault wave recording device |
| CN111399762A (en) * | 2019-11-27 | 2020-07-10 | 杭州海康威视系统技术有限公司 | Data storage method, device and storage system |
| CN114636875A (en) * | 2022-02-16 | 2022-06-17 | 西安奇点能源技术有限公司 | Fault recording method and device, storage medium and energy storage converter |
| CN114860164A (en) * | 2022-04-27 | 2022-08-05 | 浙江阳光照明电器集团股份有限公司 | Embedded system data storage structure and power failure data recovery method |
| CN115453226A (en) * | 2022-08-05 | 2022-12-09 | 福建星云电子股份有限公司 | Fault recording method and system for energy storage converter |
-
2023
- 2023-05-22 CN CN202310573849.7A patent/CN116303481B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20020162014A1 (en) * | 2001-02-23 | 2002-10-31 | Power Measurement, Ltd. | Intelligent electronic device with assured data storage on powerdown |
| JP2002150711A (en) * | 2001-08-29 | 2002-05-24 | Toshiba Corp | Information recording/reproducing device and its method |
| CN101751389A (en) * | 2008-12-18 | 2010-06-23 | 浙江省电力公司 | Steady state data search method for transformer |
| CN107819328A (en) * | 2017-09-27 | 2018-03-20 | 国家电网公司 | A kind of storage method and device of electric network fault data |
| CN109633331A (en) * | 2018-12-27 | 2019-04-16 | 中国南方电网有限责任公司 | A kind of date storage method and fault wave recording device |
| CN111399762A (en) * | 2019-11-27 | 2020-07-10 | 杭州海康威视系统技术有限公司 | Data storage method, device and storage system |
| CN114636875A (en) * | 2022-02-16 | 2022-06-17 | 西安奇点能源技术有限公司 | Fault recording method and device, storage medium and energy storage converter |
| CN114860164A (en) * | 2022-04-27 | 2022-08-05 | 浙江阳光照明电器集团股份有限公司 | Embedded system data storage structure and power failure data recovery method |
| CN115453226A (en) * | 2022-08-05 | 2022-12-09 | 福建星云电子股份有限公司 | Fault recording method and system for energy storage converter |
Non-Patent Citations (1)
| Title |
|---|
| 郑煜: "基于IEC61850智能变电站数据分析关键技术", 中国优秀硕士学位论文全文数据库 工程科技II辑, pages 042 - 78 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116578248A (en) * | 2023-07-12 | 2023-08-11 | 上海泰矽微电子有限公司 | Data processing method, apparatus, and computer readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN116303481B (en) | 2023-09-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11797191B2 (en) | Systems and methods for storing data in SSD | |
| CN106021013B (en) | Non-volatile memory device and operation method thereof | |
| KR102625637B1 (en) | Data storage device and operating method thereof | |
| US8370720B2 (en) | Mass storage device and method for offline background scrubbing of solid-state memory devices | |
| CN109002262B (en) | Data management for data storage devices | |
| CN116303481B (en) | Storage method, device, equipment and storage medium for fault wave recording data | |
| CN101520787B (en) | Method for storing real-time data | |
| KR102140592B1 (en) | Data storage device | |
| CN105893184B (en) | A kind of incremental backup method and device | |
| CN106462480A (en) | Techniques for handling errors in persistent memory | |
| CN107076797B (en) | Testing semiconductor memory power consumption based on executed access commands | |
| TW201248640A (en) | Error estimation module and estimation method thereof for flash memory | |
| US20120084028A1 (en) | Framework and Methodology for a Real-Time Fine-Grained Power Profiling with Integrated Modeling | |
| CN104516471A (en) | Method and device for managing power supply of storage system | |
| CN102207897A (en) | Incremental backup method | |
| CN109240870A (en) | A kind of solid state hard disk Fault Locating Method and relevant apparatus | |
| CN108549591A (en) | A kind of black box device and its implementation of embedded system | |
| CN103718151A (en) | Document processing method and storage device | |
| CN108008908B (en) | Method and device for controlling data on SD card | |
| CN101290621B (en) | Safe digital card memory search method | |
| CN109144766B (en) | Data storage and reconstruction method and device and electronic equipment | |
| CN112631526A (en) | Method for reading and writing same memory by main cycle and interrupt cycle of embedded system | |
| CN104123205A (en) | Method and device for detecting CPU over-clock working state | |
| CN202929443U (en) | Hand-held CAN bus data analytical equipment | |
| CN201994075U (en) | Solid-state electronic disk capable of authentic data destruction based on CPLD (complex programmable logic device) |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |