A method, system and device for storing drive debug data and an electronic device

Abstract

Embodiments of the present application provide a kind of storage method, system, device and electronic equipment of driving debugging data, applied to electronic paper equipment debugging technical field.The method comprises: obtaining the debugging data file involved in the driving waveform debugging process of electronic paper equipment;The driving debugging data of specified data dimension is parsed from the debugging data file;Wherein, specified data dimension is the data dimension that is pre-set in each data dimension in debugging data file, and the data dimension that needs to be stored;Based on driving debugging data, determine the index data for the driving waveform debugging of electronic paper equipment;Driving debugging data and index data are stored.Through the present scheme, it can provide data support for the feedback processing such as optimization, backtracking and failure analysis of driving waveform debugging.

Description

Technical Field

[0001] This invention relates to the field of electronic paper device debugging technology, and in particular to a method, system, device and electronic device for storing drive debugging data. Background Technology

[0002] Electronic paper devices, also known as electronic ink displays, are widely used in electronic price tags, e-books, and other fields due to their advantages such as a reading experience highly similar to paper, eye-friendly design, suitability for extended reading sessions, and long battery life. Electronic paper devices primarily utilize electrophoresis technology for display. Simply put, electronic paper devices contain colored charged particles. When a voltage is applied to electrodes on either side of these particles, the particles undergo electrophoretic movement under the influence of the electric field, resulting in attraction and repulsion by the electrodes, thus achieving bright or dark display states.

[0003] During the production and debugging of electronic paper equipment, it is necessary to perform drive waveform (WF) debugging. The drive waveform is a voltage waveform applied to the electrodes on both sides of the colored charged particles, thereby causing the colored charged particles to undergo electrophoretic motion. The purpose of driving waveform debugging is to achieve bistable (bright and dark) display in electronic paper equipment. The quality of the drive waveform debugging determines the display effect of the electronic paper equipment.

[0004] In related technologies, the lack of data recording during the debugging of drive waveforms for electronic paper devices makes it impossible to perform subsequent optimization, backtracking, and failure analysis feedback processing of the drive waveform debugging. Summary of the Invention

[0005] The purpose of this invention is to provide a method, system, device, and electronic device for storing drive debugging data, which can provide data support for feedback processing such as optimization, backtracking, and failure analysis of drive waveform debugging.

[0006] In a first aspect, embodiments of the present invention provide a method for storing driver debugging data, the method comprising:

[0007] Obtain the debugging data files involved in the drive waveform debugging process of the electronic paper device;

[0008] The driver debugging data of a specified data dimension is obtained by parsing the debugging data file; wherein, the specified data dimension is a preset data dimension that needs to be stored among the data dimensions in the debugging data file;

[0009] Based on the drive debugging data, determine the index data for debugging the drive waveform of the electronic paper device;

[0010] The driver debugging data and the indicator data are stored.

[0011] Optionally, determining the index data for debugging the drive waveform of the electronic paper device based on the drive debugging data includes:

[0012] The driver debugging data is converted to a standard format to obtain standard debugging data;

[0013] Using the standard debugging data, the indicator data for debugging the drive waveform of the electronic paper device are determined.

[0014] Optionally, the drive debugging data includes at least one of voltage frame data and pulse matrix data; the voltage frame data indicates the voltage value of each colored charged particle applied by the electronic paper device during the drive waveform debugging process; the pulse matrix data is used to indicate the application frequency and cycle information of the voltage applied by each colored charged particle in the voltage frame data.

[0015] The conversion of the driver debugging data to a standard format to obtain standard debugging data includes:

[0016] In the case where the drive debugging data includes the voltage frame data, each voltage value in the voltage frame data is converted into a voltage value in a standard voltage format, and / or the voltage frame data is converted into voltage frame data in a standard frame format;

[0017] If the drive debugging data includes the pulse matrix data, the pulse matrix data is converted into pulse matrix data in a standard pulse format;

[0018] The converted voltage values ​​in the standard voltage format, the voltage frame data in the standard frame format, and / or the pulse matrix data in the standard pulse format are used as standard debugging data.

[0019] Optionally, the standard debugging data includes voltage frame data in the standard frame format and pulse matrix data in the standard pulse format; the method further includes:

[0020] Based on the voltage frame data in the standard frame format and the pulse matrix data in the standard pulse format, a waveform diagram of the driving waveform of the electronic paper device during the debugging process of the electronic paper device driving waveform is generated.

[0021] The waveform diagram is shown.

[0022] Optionally, determining the index data for debugging the drive waveform of the electronic paper device using the standard debugging data includes:

[0023] For each indicator requirement dimension, the corresponding debugging data is extracted from the standard debugging data, and the extracted debugging data is calculated according to the indicator calculation method corresponding to the indicator requirement dimension to obtain the indicator data under the indicator requirement dimension for debugging the electronic paper device drive waveform.

[0024] Optionally, storing the driver debugging data and the indicator data includes:

[0025] The driver debugging data, the indicator data, and the standard debugging data are stored in different storage locations, respectively.

[0026] Optionally, the method further includes:

[0027] When a data query instruction is received, the data to be queried by the data query instruction is determined from the storage locations of the driver debugging data, the indicator data, and / or the standard debugging data; and the data query instruction is responded to based on the determined data.

[0028] Optionally, the indicator data includes indicator data from each debugging stage during the debugging process of the electronic paper device drive waveform;

[0029] After determining the index data for debugging the drive waveform of the electronic paper device based on the drive debugging data, the method further includes:

[0030] For each debugging stage in the electronic paper device drive waveform debugging process, a data statistics chart of each indicator data in that debugging stage is generated; the data statistics chart is displayed.

[0031] Optionally, after parsing the driver debugging data of a specified data dimension from the debugging data file, and before determining the indicator data for debugging the electronic paper device's driver waveform based on the driver debugging data, the method further includes:

[0032] Generate identification information for the driver debugging data as target identification information; write the target identification information into a message queue; when the target identification information is read from the message queue, execute the step of determining the index data for debugging the driver waveform of the electronic paper device based on the driver debugging data;

[0033] And / or,

[0034] When the preset task execution cycle is reached, the indicator data for determining the drive waveform debugging of the electronic paper device based on the drive debugging data is executed.

[0035] Optionally, parsing the driver debugging data of a specified data dimension from the debugging data file includes:

[0036] Extract data from the specified data dimensions from the debug data file as initial screening data;

[0037] The initial screening data is subjected to structured data transformation to obtain the transformed data, which is used as the driving debugging data for the specified data dimension.

[0038] Optionally, the step of performing structured data transformation on the initial screening data to obtain the transformed data includes:

[0039] Determine the preset data labels corresponding to the specified data dimension;

[0040] The initial screening data is written into the field values ​​with the data labels as field names to obtain the transformed data.

[0041] Optionally, the debugging data file includes at least one of a debugging parameter file, a debugging result file, and a debugging standard file; wherein, the debugging parameter file records the waveform parameters of the driving waveform to be applied during the debugging process of the electronic paper device; the debugging result file records the actual display quality data of the electronic paper device after the driving waveform is applied according to the waveform parameters; and the debugging standard file records the standard display quality data that the electronic paper device needs to meet.

[0042] The step of extracting data of a specified dimension from the debug data file as initial screening data includes:

[0043] If the debug file data includes the debug parameter file, the recorded waveform parameters are extracted from the debug parameter file;

[0044] If the debug file data includes the debug result file, extract the recorded actual display quality data from the debug result file;

[0045] If the debug file data includes the debug standard file, extract the recorded standard display quality data from the debug standard file;

[0046] The extracted waveform parameters, the actual display quality data, and / or the standard display quality data are used as the initial screening data.

[0047] Secondly, embodiments of the present invention provide a storage system for drive debugging data, the system comprising: a data source, a data upload module, and a data processing module, wherein the data source stores debugging data files involved in the drive waveform debugging process of the electronic paper device, wherein:

[0048] The data upload module is used to read the debug data file from the data source and transmit the debug data file to the data processing module;

[0049] The data processing module is used to, after receiving the debug data file transmitted by the data upload module, parse the debug data file to obtain drive debug data of a specified data dimension from the debug data file; wherein, the specified data dimension is a preset data dimension that needs to be stored among the data dimensions in the debug data file; based on the drive debug data, determine the index data for debugging the drive waveform of the electronic paper device; and store the drive debug data and the index data.

[0050] Optionally, the system further includes: a display module;

[0051] The display module is used to display the waveform diagram of the driving waveform of the electronic paper device during the debugging process of the driving waveform of the electronic paper device, and / or the data statistics diagram of each indicator data in each debugging stage during the debugging process of the driving waveform of the electronic paper device;

[0052] The waveform is determined based on voltage frame data in a standard frame format and pulse matrix data in a standard pulse format. The voltage frame data in the standard frame format is the data after converting the drive debugging data to a standard frame format when the drive debugging data includes voltage frame data. The pulse matrix data in the standard pulse format is the data after converting the pulse matrix data to a standard pulse format when the drive debugging data includes pulse matrix data. The voltage frame data indicates the voltage value applied by each colored charged particle during the drive waveform debugging process of the electronic paper device. The pulse matrix data is used to indicate the application frequency and cycle information of the voltage applied by each colored charged particle in the voltage frame data.

[0053] Thirdly, embodiments of the present invention provide a storage device for driver debugging data, the device comprising:

[0054] The file acquisition module is used to acquire the debugging data files involved in the driving waveform debugging process of the electronic paper device;

[0055] The data parsing module is used to parse the driver debugging data of a specified data dimension from the debugging data file; wherein, the specified data dimension is a preset data dimension that needs to be stored among the data dimensions in the debugging data file;

[0056] The data conversion module is used to determine the index data for debugging the drive waveform of the electronic paper device based on the drive debugging data;

[0057] The data storage module is used to store the driver debugging data and the indicator data.

[0058] Fourthly, embodiments of the present invention provide an electronic device, including a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus;

[0059] Memory, used to store computer programs;

[0060] When a processor executes a program stored in memory, it implements any of the steps described in the first aspect.

[0061] Fifthly, embodiments of the present invention provide a computer-readable storage medium storing a computer program, wherein the computer program, when executed by a processor, implements the steps of any of the methods described in the first aspect.

[0062] In a sixth aspect, embodiments of the present invention provide a computer program product containing instructions that, when run on a computer, cause the computer to perform any of the methods described in the first aspect.

[0063] Beneficial effects of the embodiments of the present invention:

[0064] The present invention provides a method for storing drive debugging data, which involves acquiring debugging data files related to the drive waveform debugging process of an electronic paper device; parsing drive debugging data of a specified data dimension from the debugging data files; wherein the specified data dimension is a preset data dimension that needs to be stored among the data dimensions in the debugging data file; determining indicator data for the drive waveform debugging of the electronic paper device based on the drive debugging data; and storing the drive debugging data and indicator data. Since drive debugging data of a specified data dimension can be parsed from the debugging data files, and indicator data for the drive waveform debugging of the electronic paper device can be further determined, and then the drive debugging data and indicator data can be stored, the storage of data during the drive waveform debugging process of the electronic paper device is realized, thereby providing data support for feedback processing such as optimization, backtracking, and failure analysis of drive waveform debugging.

[0065] Of course, implementing any product or method of the present invention does not necessarily require achieving all of the advantages described above at the same time. Attached Figure Description

[0066] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, 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 the present invention. For those skilled in the art, other embodiments can be obtained based on these drawings.

[0067] Figure 1 A flowchart illustrating the method for storing driver debugging data provided in an embodiment of the present invention;

[0068] Figure 2a A waveform diagram of a driving waveform for a black charged particle provided in an embodiment of the present invention;

[0069] Figure 2b A waveform diagram of a driving waveform for a white charged particle provided in an embodiment of the present invention;

[0070] Figure 2c A waveform diagram of a driving waveform for a red charged particle provided in an embodiment of the present invention;

[0071] Figure 2d A waveform diagram of a reference voltage provided in an embodiment of the present invention;

[0072] Figure 3 This is a schematic diagram of a data statistics chart provided in an embodiment of the present invention;

[0073] Figure 4 This is a schematic diagram of the structure of a data warehouse provided in an embodiment of the present invention;

[0074] Figure 5 This is a schematic diagram of a real-time processing method provided in an embodiment of the present invention;

[0075] Figure 6 This is a schematic diagram of an offline processing method provided in an embodiment of the present invention;

[0076] Figure 7 This is a schematic diagram of the structure of the driver debugging data storage system provided in an embodiment of the present invention;

[0077] Figure 8 This is another schematic diagram of the storage system for driver debugging data provided in an embodiment of the present invention;

[0078] Figure 9 This is a framework diagram of the driver debugging data storage system provided in an embodiment of the present invention;

[0079] Figure 10 This is a schematic diagram of the structure of the storage device for driver debugging data provided in an embodiment of the present invention;

[0080] Figure 11 This is a schematic diagram of the structure of the electronic device provided in an embodiment of the present invention. Detailed Implementation

[0081] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art based on this application are within the scope of protection of the present invention.

[0082] To provide data support for feedback processing such as optimization, backtracking, and failure analysis of drive waveform debugging, embodiments of the present invention provide a method, apparatus, and electronic device for storing drive debugging data.

[0083] It should be noted that, in specific applications, the embodiments of the present invention can be applied to various electronic devices, such as personal computers, servers, mobile phones, and other devices with data processing capabilities. Furthermore, the method for storing driver debugging data provided in the embodiments of the present invention can be implemented through software, hardware, or a combination of both.

[0084] In one embodiment, the application scenario of this invention can be in the production and debugging of electronic paper equipment. During the production and debugging process of electronic paper equipment, it is necessary to debug the drive waveform of the electronic paper equipment to determine the drive waveform that meets the display requirements of the electronic paper equipment. In this scenario, this invention can be applied to a data analysis platform deployed in the electronic paper equipment production and debugging scenario. This data analysis platform can be used to build an automated debugging process during the electronic paper equipment production and debugging process. Simply put, based on this data analysis platform, an automated debugging process for electronic paper equipment can be built, thereby reducing labor costs and improving the digital production efficiency of the entire electronic paper equipment production line compared to the manual debugging method in the prior art. This data analysis platform can be composed of a single server or multiple servers, and it can also deploy components such as control terminals and display terminals as needed.

[0085] The method for storing driver debugging data provided in this embodiment of the invention may include:

[0086] Obtain the debugging data files involved in the drive waveform debugging process of the electronic paper device;

[0087] The driver debugging data of the specified data dimension is obtained by parsing from the debugging data file; where the specified data dimension is the preset data dimension that needs to be stored among the data dimensions in the debugging data file;

[0088] Based on the driver debugging data, determine the indicator data for debugging the driver waveform of electronic paper devices;

[0089] Store driver debugging data and indicator data.

[0090] In the above-described scheme of this invention, drive debugging data of a specified data dimension can be parsed from the debugging data file, and index data for driving waveform debugging of electronic paper devices can be further determined. Then, the drive debugging data and index data are stored, realizing the storage of data during the driving waveform debugging process of electronic paper devices, thereby providing data support for feedback processing such as optimization, backtracking and failure analysis of driving waveform debugging.

[0091] The method for storing driver debugging data provided in the embodiments of the present invention will now be described in detail with reference to the accompanying drawings.

[0092] like Figure 1 As shown, this embodiment of the invention provides a method for storing driver debugging data, including steps S101-S104, wherein:

[0093] S101, Obtain the debugging data file involved in the drive waveform debugging process of the electronic paper device;

[0094] In this step, the debugging data file may include various files involved in the debugging process of the electronic paper device during the drive waveform debugging, such as debugging parameter files, debugging result files, debugging standard files, user information files, etc. Optionally, the debugging data file obtained in this step may be at least one of the above types of files.

[0095] The aforementioned debugging parameter file records the waveform parameters of the driving waveform that need to be applied during the debugging process of the electronic paper device, such as at least one of the following: temperature, frequency, voltage of each colored charged particle, and pulse matrix data during driving waveform debugging.

[0096] Different types of electronic paper devices may contain different types of colored charged particles, and thus the types of voltages of the colored charged particles may also differ. For example, a black and white electronic paper device contains only black charged particles and white dot particles, and thus the voltages of the colored charged particles include the black voltage for black charged particles, the white voltage for white charged particles, and the reference voltage.

[0097] For electronic paper devices capable of displaying other colors, in addition to the black and white charged particles mentioned above, the colored charged particles they contain may also include colored charged particles, such as red charged particles. Therefore, the voltage of each colored charged particle, in addition to the black voltage, white voltage, and reference voltage mentioned above, may also include a voltage specific to the colored charged particles, such as a red voltage specific to the red charged particles.

[0098] The voltages of the aforementioned colored charged particles can be recorded in the voltage frame data within the debugging parameter file. This voltage frame data indicates the voltage value applied to each colored charged particle during the electronic paper device's drive waveform debugging process. For example, the voltage frame data could be {lvHI,lvCM,lvHI,lvCM}, where lv is the voltage identifier, HI represents the black voltage (its specific value is the magnitude of the black voltage), and CM represents the reference voltage (its specific value is the magnitude of the reference voltage).

[0099] The pulse matrix data mentioned above is used to indicate the application frequency and cycle number of each voltage in the voltage frame data. Simply put, the voltage frame data is {lvHI,lvCM,lvHI,lvCM}, and the pulse matrix data is {0x01,0x21,0x00,0x04,0x10,0x06,0x02}. If the cycle of this type of pulse matrix is ​​identified as (7, 1, 4), it means that the 7th bit of the pulse matrix data, 0x02, is the large cycle number of the voltage frame data. The 1st bit of the pulse matrix data, 0x01, represents the small cycle number of the 1st voltage, lvHI, and the 2nd voltage, lvCM, in the voltage frame data. The 4th bit of the pulse matrix data, 0x01, represents the small cycle number of the 3rd voltage, lvHI, and the 4th voltage, lvCM, in the voltage frame data. In the pulse matrix data, the second bit (0x21), the third bit (0x00), the fifth bit (0x10), and the sixth bit (0x06) represent the frequency of voltage application in the corresponding voltage frame data. It should be noted that the meaning of data at different positions in the pulse matrix data varies for different types of electronic paper devices; the above (7, 1, 4) is only an example.

[0100] Based on voltage frame data and pulse matrix data, the driving waveform can be determined. Then, during the debugging process, the driving waveform that needs to be applied during the debugging of the electronic paper device can be determined according to the debugging parameter file.

[0101] The aforementioned debugging result file records the actual display quality data of the electronic paper device after applying the driving waveform according to the waveform parameters. During the debugging process of the electronic paper device's driving waveform, it is necessary to measure the display quality data of the electronic paper device after applying the driving waveform according to the waveform parameters. This display quality data is used to evaluate the color rendering effect of the electronic paper device. For example, the Lab color model can be used to evaluate the color rendering effect of the EPD screen. The Lab color model is a color model established by an international standard for color measurement. The Lab color model is neither dependent on light nor on pigments; it is a color model determined by the International Commission on Illumination that theoretically includes all colors visible to the human eye. The Lab color model is a device-independent color system and also a color system based on physiological characteristics. This means that the Lab color model uses a digital method to describe human visual perception. In the Lab color model's color space, the L component represents the brightness of a pixel, with a value range of [0, 100], representing pure black to pure white; the a component represents the range from red to green, with a value range of [127, -128]; and the b component represents the range from yellow to blue, with a value range of [127, -128].

[0102] For example, taking an electronic paper device containing white, black, and red charged particles as an example, this means that the electronic paper device can display three colors: white, black, and red. For each displayed color, it is necessary to measure the L, a, and b components of the Lab color model when the electronic paper device displays that color after applying a driving waveform according to the waveform parameters. Optionally, measurements can be performed separately at different temperatures to obtain the L, a, and b components of the Lab color model for each color displayed by the electronic paper device when applying a driving waveform according to the waveform parameters at different temperatures. For example, the measured actual display quality data is shown in Table 1:

[0103] Table 1

[0104]

[0105] Table 1 shows that the L, a, and b components of the Lab color model for each color displayed by the electronic paper device at different temperatures were measured twice when the driving waveform was applied according to the waveform parameters. Two sets of data were obtained. Taking the display of white at 0° as an example, after the electronic paper device applied the driving waveform according to the waveform parameters, the first measurement showed that the L component was 66.47, the a component was -2.18, and the b component was -0.61. The second measurement showed that the L component was 66.13, the a component was -2.14, and the b component was -0.85.

[0106] The aforementioned standard debugging document records the standard display quality data that electronic paper devices must meet. This standard display quality data is used to determine the standards by which an electronic paper device meets display quality requirements. When evaluating the color rendering effect of the EPD screen using the Lab color model, the aforementioned standard display quality data may include the value range of at least one of the L, a, and b components. Values ​​within the range indicate that the display quality meets the requirements, while values ​​outside the range indicate that the requirements are not met. Optionally, the data can be further divided according to temperature, i.e., the value range of each component at different temperatures.

[0107] For example, the standard display quality data that electronic paper devices need to meet are shown in Table 2:

[0108] Table 2

[0109]

[0110]

[0111] As shown in Table 2, when displaying red, the electronic paper device only has quality requirements for the L and a components of the Lab color model; when displaying black, it only has quality requirements for the a component of the Lab color model; and when displaying white, it only has quality requirements for the b component of the Lab color model. Taking a temperature range of 30°C to 40°C as an example, when the electronic paper device displays red, the maximum value of the L component is 29, and the minimum value is 26. That is, when the electronic paper device is adjusted for driving waveform within the temperature range of 30°C to 40°C, if the measured L component is greater than or equal to 26 and less than or equal to 29 when the electronic paper device displays red, the display requirements are met; otherwise, the display requirements are not met.

[0112] The aforementioned user information file may record user information, which may include relevant information about the customer requiring the electronic paper device to be debugged, such as customer name and customer identification. Alternatively, the aforementioned user information may also include information about the personnel debugging the electronic paper device, which is also possible.

[0113] The aforementioned debugging parameter files, debugging result files, debugging standard files, user information files, and other types of files can be stored in a data source, which can include various types of databases, such as MySQL (a relational database management system), file storage databases, or log databases.

[0114] After the electronic paper device performs one or more drive waveform debugging processes, it can read various data files involved in the one or more drive waveform debugging processes from the database.

[0115] S102, parse the driver debugging data of the specified data dimension from the debugging data file; wherein, the specified data dimension is the preset data dimension that needs to be stored among the data dimensions in the debugging data file;

[0116] After obtaining the debug data file, the driver debug data for a specified data dimension can be parsed from it. The specified data dimension refers to the pre-defined data dimension within the debug data file that needs to be stored. For example, if the debug data file includes a debug parameter file, the data for the specified data dimension can be waveform parameters; if the debug data file includes a debug result file, the data for the specified data dimension can be actual display quality data; and if the debug data file includes a debug standard file, the data for the specified data dimension can be standard display quality data.

[0117] In one implementation, after obtaining the debug data file, data of a specified data dimension can be extracted from the debug data file as preliminary screening data. Then, the preliminary screening data is subjected to structured data transformation to obtain the transformed data, which is used as the driving debug data of the specified data dimension.

[0118] The file formats of different debugging data files may differ. For example, debugging parameter files can be language source program files (such as files with the .h or .c extension used by C language), while debugging result files and debugging standard files can be Excel (spreadsheet) files.

[0119] Different file formats of debug data files can be parsed using different methods. The specific parsing method can be matched with the file format of the debug data file to extract content data, and then filter data of a specified dimension from the content data. This filtering process can use methods such as keyword search and template matching to extract data of a specified dimension from the debug data file.

[0120] In one implementation, the extracted data from a specified dimension can be directly used as driver debugging data for subsequent use. Alternatively, in another implementation, the extracted data can be used as initial screening data, and further, a structured data transformation can be performed on the initial screening data to obtain structured data, which can then be used as driver debugging data. It should be noted that if the initial screening data itself is structured data, the structured data transformation process can be skipped, and the initial screening data can be directly used as driver debugging data. Through structured data transformation, the acquired driver debugging data can be made structured, thus facilitating subsequent storage, processing, and analysis of the driver debugging data.

[0121] Optionally, preset data labels corresponding to the specified data dimension can be determined, and then the initial screening data can be written into the field value with the data label as the field name to obtain the transformed data. For example, if the specified data dimension is voltage, the initial screening data includes voltage values, and the data label for the voltage dimension is voltage. Then, the extracted voltage values ​​can be written into the field value with voltage as the field name to obtain the transformed data.

[0122] In one implementation, the aforementioned debug data file may include at least one of a debug parameter file, a debug result file, and a debug standard file. In this case, if the debug file data includes a debug parameter file, the recorded waveform parameters can be extracted from the debug parameter file; if the debug file data includes a debug result file, the recorded actual display quality data can be extracted from the debug result file; if the debug file data includes a debug standard file, the recorded standard display quality data can be extracted from the debug standard file; and then the extracted waveform parameters, actual display quality data, and / or standard display quality data are used as initial screening data.

[0123] It should be emphasized that, in addition to the waveform parameters, actual display quality data and standard display quality data mentioned above, other data recorded in each file can also be extracted as needed. For example, in addition to waveform parameters, the debugging parameter file can also contain information such as the version number of the waveform parameters. This kind of information can also be extracted as needed and used as initial screening data.

[0124] S103, Based on the driver debugging data, determine the index data for debugging the driver waveform of the electronic paper device;

[0125] To improve the efficiency of later optimization, backtracking, and failure analysis of drive waveform debugging, in addition to the stored drive debugging data, it is also possible to determine the index data for drive waveform debugging of electronic paper devices based on the drive debugging data. The required index data can be determined in conjunction with actual needs.

[0126] When the drive debugging data includes waveform parameters, this indicator data can be waveform-related metrics, such as the average voltage applied to each colored charged particle, the total voltage of each colored charged particle, the distribution of driving voltage values ​​for each colored charged particle, the driving voltage of each colored charged particle, and the cumulative voltage of each colored charged particle. When the drive debugging data includes actual display quality data, this indicator data can be the mean value and distribution range of each component. When the drive debugging data includes waveform parameters, actual display quality data, and standard display quality data, a comparison between the actual display quality data and the standard display quality data can be used to determine whether the electronic paper device meets the display quality requirements when applying the driving voltage according to the waveform parameters; that is, whether the drive waveform debugging of the electronic paper device has passed, which can be used as indicator data.

[0127] In one embodiment, step S104 may include steps A1-A2, wherein:

[0128] Step A1: Convert the driver debugging data to a standard format to obtain standard debugging data;

[0129] Because the drive debugging data of different electronic paper devices may have different formats, for example, the red voltage in the waveform parameters of electronic paper device A is marked as RV6_5 in the form of a string, while the red voltage in the waveform parameters of electronic paper device B is marked as 0x32 in the form of hexadecimal. Although both can represent the magnitude of the red voltage, the difference in data format increases the difficulty of managing the data involved in the drive waveform debugging process of different electronic paper devices, and makes it inconvenient to perform statistical calculations of indicator data.

[0130] To reduce the difficulty of managing data involved in the debugging of drive waveforms for different electronic paper devices, and to facilitate the statistical calculation of indicator data, this embodiment can first convert the drive debugging data into a standard format to obtain standard debugging data.

[0131] The standard format conversion refers to converting driver debugging data into a specified standard format. The standard format can differ for each category of driver debugging data. For example, driver debugging data includes waveform parameters such as voltage, temperature, and frequency. These parameters may be represented in different formats in the debugging parameter files of different electronic paper devices. For instance, in the example above, the voltage value might be recorded as a string or in hexadecimal format. Therefore, a standard format needs to be preset for each type of driver debugging data. For example, the red voltage RV6_5 of electronic paper device A above should be converted to 6.5V, and the red voltage 0x32 of electronic paper device B above should be converted to (3*16+2)*0.1=5.0V. This ensures a unified format for the red voltage, facilitating the management of red voltages across different electronic paper devices.

[0132] In one implementation, the aforementioned drive debugging data may include at least one of voltage frame data and pulse matrix data; wherein, the voltage frame data indicates the voltage value applied by each colored charged particle during the drive waveform debugging process of the electronic paper device; and the aforementioned pulse matrix data is used to indicate the application frequency and cycle information of the voltage applied by each colored charged particle in the voltage frame data. The relevant concepts have been introduced in the foregoing sections and will not be repeated here.

[0133] In this case, if the drive debugging data includes voltage frame data, each voltage value in the voltage frame data can be converted to a voltage value in a standard voltage format, and / or the voltage frame data can be converted to voltage frame data in a standard frame format. Different electronic paper devices may have different formats for recording voltage values ​​and different specific frame formats. Therefore, for voltage values, each voltage value in the voltage frame data can be converted to a voltage value in a standard voltage format, such as converting the aforementioned red voltage RV6_5 to 6.5V. For the frame format, it can be converted to a frame format of {A,B,C,D}, where A, B, C, and D are set to the voltage value or reference voltage value of a corresponding colored charged particle as required, such as {lvHI,lvCM,lvHI,lvCM} in the aforementioned example.

[0134] When the driver debugging data includes pulse matrix data, the pulse matrix data is converted into pulse matrix data in a standard pulse format. Since the position of the cycle marker may vary in the pulse matrix data of different electronic paper devices, the voltage pulse matrix needs to be normalized. Optionally, the voltage pulse matrix data can be combined with the cycle marker bit information to perform a standard pulse format transformation. Optionally, the above standard pulse format transformation can be {f1_value,f2_value,f3_value,f4_value,big_cycle,small_cycle1,small_cycle2}, where fn_value represents the application frequency of the voltage at the nth bit in the voltage frame data, where n takes the value 1, 2, 3, or 4; big_cycle represents the number of large cycles in the voltage frame data; small_cycle1 represents the number of small cycles for the first and second voltage bits in the voltage frame data; and small_cycle2 represents the number of small cycles for the second and third voltage bits in the voltage frame data. For example, if the pulse matrix data is {0x01,0x21,0x00,0x04,0x10,0x06,0x02}, and the pulse matrix cycle is (7, 1, 4), then by converting it according to the above standard pulse format, the converted voltage pulse matrix data can be obtained as {0x21,0x00,0x10,0x06,0x02,0x01,0x04}. It should be noted that the meaning of each position in the above standard pulse format is only illustrative; the specific meaning of each position can be set according to requirements.

[0135] By converting the data to a standard format, code decoupling can be achieved, so that the code for data logic calculation does not need to be changed with the model of the electronic paper device, which facilitates the later code maintenance work and makes it easier to manage various types of data involved in the debugging of the drive waveform of different models of electronic paper devices.

[0136] After converting the voltage values ​​in standard voltage format, the voltage frame data in standard frame format, and / or the pulse matrix data in standard pulse format, the converted voltage values ​​in standard voltage format, the voltage frame data in standard frame format, and / or the pulse matrix data in standard pulse format can be used as standard debugging data.

[0137] Step A2: Using standard debugging data, determine the indicator data for debugging the drive waveform of the electronic paper device.

[0138] After obtaining the standard debugging data, the performance indicators for debugging the drive waveform of the electronic paper device can be determined using this data. Since the drive debugging data for different signals of the electronic paper device has been converted to a standard format, the performance indicators can be calculated using the standard debugging data according to the standard format calculation method.

[0139] In one implementation, for each indicator requirement dimension, debugging data corresponding to that indicator requirement dimension can be extracted from the standard debugging data, and the extracted debugging data can be calculated according to the indicator calculation method corresponding to that indicator requirement dimension to obtain the indicator data under that indicator requirement dimension for debugging the electronic paper device drive waveform.

[0140] The aforementioned indicator requirement dimension refers to the dimension of the indicator data that needs to be calculated. For example, if it is necessary to calculate the average voltage applied by each colored charged particle, then the indicator requirement dimension is the average voltage. Based on this, the debugging data corresponding to this indicator requirement dimension is the standard format voltage of each colored charged particle in the standard debugging data. The indicator calculation method corresponding to this indicator requirement dimension is the mean calculation method, that is, it is necessary to obtain the standard format voltage of each colored charged particle from the standard debugging data, and then perform mean calculation to obtain the average voltage applied by each colored charged particle.

[0141] S104 stores driver debugging data and indicator data.

[0142] After obtaining the driver debugging data and indicator data, the driver debugging data and indicator data can be stored.

[0143] In one approach, driver debugging data and indicator data can be written to the same storage location. Further, to improve the efficiency of data retrieval or adjustment, driver debugging data and indicator data can be stored in different locations. Optionally, driver debugging data can be written to a preset first storage location, while indicator data can be written to a preset second storage location. By storing data in separate locations, driver debugging data and indicator data can operate independently. When querying or modifying driver debugging data, this can be done directly through the interface of the first storage location, and when querying or modifying indicator data, it can be done directly through the interface of the second storage location. Firstly, distributed storage of different data ensures that the data in a single storage location is not excessive, thus avoiding the problem of low query and modification efficiency due to excessive data. Secondly, distributed data storage simplifies the storage logic of each data point during the driver waveform debugging process, facilitating adjustment and retrieval. When errors or rule changes occur, only local data adjustments are needed.

[0144] The first storage location mentioned above can be a preset location for storing driver debugging data. For example, the first storage location can be a specified database for storing driver debugging data. The second storage location mentioned above can be a preset location for storing indicator data. For example, the second storage location can be a specified database for storing indicator data.

[0145] Optionally, depending on the type of driver debugging data, the aforementioned database can be stored using different types of databases. For example, if the driver debugging data includes user information extracted from a user information file, the aforementioned database can include a transactional database that facilitates CRUD operations.

[0146] When the aforementioned driver debugging data includes at least one of waveform parameters, actual display quality data, and standard display quality data, the aforementioned database may include an analytical database that facilitates analysis and calculation. For example, this analytical database may be a ClickHouse database, which is a columnar database management system for Online Analytical Processing (OLAP). Compared to relational databases, which primarily perform CRUD operations and emphasize transaction consistency, ClickHouse database reads column data for calculation, rather than entire rows of data, thus reducing I / O (Input / Output) consumption and making it suitable for complex data analysis.

[0147] In one implementation, after parsing the driver debugging data, the driver debugging data can be written into a data table, and then the data table can be written into the first storage location. During this process, to facilitate subsequent searching, analysis, and processing of the driver debugging data, identification information for the data table, such as the table name, can be generated.

[0148] In one implementation, the first storage location can be the data storage layer in a data warehouse. Based on this, the identification information of the data tables can be stored in the dimension tables of the data dictionary. A dimension table is a structured table used to describe the categorical attributes of data. It contains a set of attributes for grouping, filtering, and sorting data, such as time, geographic location, product, and customer, and is used to associate with the fact table to provide richer data analysis and reporting capabilities. Each dimension table needs to record detailed information about its fields, data types, data sources, data processing logic, etc.

[0149] In the above-described scheme of this invention, the driving debugging data of a specified data dimension is parsed from the debugging data file, and then the driving debugging data is written into a preset first storage location. This realizes the storage of data during the debugging process of the electronic paper device driving waveform, thereby providing data support for feedback processing such as optimization, backtracking, and failure analysis of driving waveform debugging.

[0150] In another embodiment of the present invention, to further provide richer data for improving the feedback processing of drive waveform debugging, after the standard debugging data is calculated in step A1 above, the drive debugging data, indicator data, and standard debugging data can be stored in different storage locations respectively. Thus, according to the needs of subsequent processing, the required data can be retrieved from the stored drive debugging data, indicator data, and standard debugging data. Storing the drive debugging data, indicator data, and standard debugging data in different storage locations allows for distributed storage of these data. Firstly, distributed storage ensures that the data in a single storage location is not excessive, thus avoiding the problem of low query and modification efficiency due to excessive data. Secondly, distributed storage simplifies the storage logic of each data point during the drive waveform debugging process, facilitating adjustment and retrieval. When errors or rule changes occur, only local data adjustments are needed.

[0151] In one implementation, driver debugging data can be written to a first storage location, indicator data to a second storage location, and then standard debugging data to a preset third storage location. The third storage location can be a preset location for storing indicator data. For example, the third storage location can be a specified database for storing standard debugging data.

[0152] Optionally, the first, second, and third storage locations can be different. The first storage location stores driver debugging data, the second storage location stores indicator data, and the third storage location stores standard debugging data. Because different data are stored in different locations, it is convenient to adjust and retrieve driver debugging data, standard debugging data, and / or indicator data. In one implementation, the first, second, and third storage locations can be different data storage layers within a data warehouse.

[0153] In another embodiment of the present invention, in order to further improve the efficiency of data retrieval for subsequent feedback processing such as optimization, backtracking and failure analysis of driving waveform debugging, the present invention embodiment can further display graphical data such as waveform diagrams and data statistical charts based on the stored various types of data.

[0154] In one implementation, when the standard debugging data includes voltage frame data in a standard frame format and pulse matrix data in a standard pulse format, a waveform diagram of the electronic paper device's driving waveform during debugging can be generated based on the voltage frame data in the standard frame format and the pulse matrix data in the standard pulse format, and then the waveform diagram can be displayed. For example, an electronic paper device containing colored charged particles of black, white, and red will be used as an example for illustration. Figure 2a As shown, this waveform diagram is a waveform diagram of the driving waveform for black charged particles, as follows. Figure 2b As shown, this waveform diagram is a waveform diagram of the driving waveform for white charged particles, such as... Figure 2c As shown, this waveform diagram is a waveform diagram of the driving waveform for red charged particles, as follows. Figure 2d As shown, this waveform diagram represents the reference voltage. The numbers on the horizontal axis indicate the frequency of the corresponding waveform cycle, and the vertical axis represents the voltage value.

[0155] In one implementation, when the indicator data includes indicator data in each debugging stage during the debugging process of the electronic paper device driving waveform, after writing the indicator data to a preset second storage location, a data statistics chart of each indicator data in each debugging stage can be generated for each debugging stage during the debugging process of the electronic paper device driving waveform; and the data statistics chart can be displayed.

[0156] The electronic paper device drive waveform debugging process includes three debugging stages: balance, shaking, and imaging. The corresponding indicator data can include data from different debugging stages. Furthermore, for each debugging stage in the electronic paper device drive waveform debugging process, based on the indicator data of that stage, a data statistics chart for each indicator data in that stage can be generated. These data statistics charts can include value distribution charts, drive voltage charts, cumulative voltage charts, etc.

[0157] Optionally, the data statistics charts for the different debugging stages mentioned above can be displayed in a drawer format, with each drawer containing data statistics charts for multi-dimensional indicators. For example... Figure 3 As shown, the data statistics charts for different debugging stages are displayed in a drawer format. In the shaking stage 1, data statistics charts for multi-dimensional indicators are displayed.

[0158] Optionally, to facilitate access for debugging personnel, the waveforms and data statistics charts shown above can be downloaded.

[0159] The solution provided in this embodiment can provide data support for feedback processing such as optimization, backtracking, and failure analysis in driving waveform debugging. Furthermore, it can display graphical data such as waveform diagrams and data statistics charts, thereby visually displaying the data involved in the driving waveform debugging process of electronic paper devices, and improving the efficiency of data retrieval during the driving waveform debugging process of electronic paper devices.

[0160] Optionally, in another embodiment of the present invention, after generating waveforms and / or data statistics in the above embodiments, the generated waveforms and / or data statistics can be written to a preset fourth storage location.

[0161] The aforementioned fourth storage location can be a preset location for storing image data. For example, the fourth storage location can be a designated database for storing image data. Optionally, the first, second, and third storage locations are different from the fourth storage location, thereby achieving distributed storage of driver debugging data, indicator data, standard debugging data, and image data. Optionally, the first storage location stores driver debugging data, the second storage location stores indicator data, the third storage location stores standard debugging data, and the fourth storage location stores waveforms and / or data statistical charts. Since different data are stored in different locations, it is convenient to adjust and retrieve driver debugging data, standard debugging data, and / or indicator data. In one implementation, the first, second, third, and fourth storage locations can be different data storage layers in a data warehouse.

[0162] For example, such as Figure 4 This embodiment provides a schematic diagram of a data warehouse structure. It includes a hierarchical data storage layer 1, a data storage layer 2, a data storage layer 3, and a data storage layer 4. Specifically, data storage layer 1 is the first storage location for storing driver debugging data; data storage layer 2 is the third storage location for storing standard debugging data; data storage layer 3 is the second storage location for storing indicator data; and data storage layer 4 is the fourth storage location for storing image data. Optionally, the data warehouse may also include a data source, which stores debugging data files involved in the driver waveform debugging process of various types of electronic paper devices. This allows the data warehouse to obtain debugging data files from the data source, parse driver debugging data from the debugging data files, and then store it in data storage layer 1. Optionally, the data warehouse may also include dimension tables for describing the classification attributes of the data.

[0163] In one implementation, the data in the data warehouse mentioned above consists of debug data files in file format. First, the structured or unstructured data files in the debug data files need to be parsed. The resulting structured driver debug data is then stored in data storage layer 1. The driver debug data undergoes simple cleaning and verification to ensure its content remains consistent with the debug data files. Data storage layer 2 can standardize the raw data from data storage layer 1 to obtain standardized business detail data. Data storage layer 3 can correlate the data from data storage layer 2 and data storage layer 1 to perform indicator calculations. It can summarize indicators for data tables based on different subject areas. For example, it can summarize and statistically analyze driver waveforms, calculate indicators for display quality data that passed tests, and perform indicator statistics for display quality data that failed tests. Data storage layer 4 can generate and store waveform diagrams or data statistical charts.

[0164] In another embodiment of the present invention, after storing the driver debugging data, standard debugging data, and / or indicator data, the embodiment also provides a query interface. Upon receiving a data query instruction, the data to be queried by the instruction can be determined from the storage locations of the driver debugging data, indicator data, and / or standard debugging data, and the data query instruction can be responded to based on the determined data. When the driver debugging data is stored in a first storage location, the indicator data is stored in a second storage location, and the standard debugging data is stored in a third storage location, the data to be queried by the instruction can be determined from the first, second, and / or third storage locations, and the data query instruction can be responded to based on the determined data. The query instruction may include the location information and / or keywords of the data to be queried, thereby utilizing the location information and / or keywords to search from the first, second, and / or third storage locations to obtain the data to be queried. Querying data using a data query instruction can improve the efficiency of data retrieval.

[0165] Optionally, in another embodiment of the present invention, after determining the index data for debugging the drive waveform of the electronic paper device based on the drive debugging data, the index data for debugging the drive waveform of the electronic paper device can be determined by real-time processing or offline processing.

[0166] For real-time processing, identification information for driver debugging data can be generated as target identification information. This identification information can be configured to uniquely identify each piece of driver debugging data, such as the processing batch number, or, if the driver debugging data is written to a data table, the identification information can be the table name. After determining the target identification information, it can be written to a message queue. When the target identification information is read from the message queue, the step of determining the index data for driver waveform debugging of the electronic paper device based on the driver debugging data is executed. Figure 5 As shown in the diagram, this embodiment of the invention provides a real-time processing schematic. It can be executed using a message middleware, with a message listening mechanism for data interaction. For each generated identifier, it can be placed in a task queue awaiting message sending. The message producer then reads the identifier from the task queue and sends it to the message queue. When the message consumer detects a message waiting to be processed in the message queue, it consumes the message and places the consumed message into the task queue of consumed messages. The message consumer retrieves the identifier from the message queue in a first-in, first-out manner and calculates the metrics for each identifier's associated data.

[0167] For offline processing, when a preset task execution cycle is reached, the system can perform tasks based on driver debugging data to determine the performance metrics for debugging the electronic paper device's driver waveform. The duration of this task execution cycle can be set as needed, for example, to 10 minutes. By setting the task execution cycle, the accuracy of the performance metrics during the electronic paper device's driver waveform debugging process can be ensured, interference between driver debugging data from different electronic paper devices can be prevented, and the process of determining the performance metrics can be simplified. Figure 6As shown in the schematic diagram of an offline processing embodiment of the present invention, the task execution cycle can be controlled by a timer. Optionally, the task of calculating indicator data can be performed periodically or at set intervals, for example, once every 10 minutes. First, the timer is configured and started. Then, it is determined whether the task execution cycle has been reached. If the task execution cycle has not been reached, the timer can sleep. After the sleep period ends, it continues to determine whether the task execution cycle has been reached. If the task execution cycle has been reached, the pending identification information within the time interval between two executions is queried. That is, based on the upload time of the driver debugging data, all identification information within the time window between the previous task execution time and the current task execution time is searched, and it is determined whether there is any pending identification information. If there is pending identification information, the corresponding driver debugging data is filtered out based on these identification information and the indicator data calculation is performed. If there is no pending identification information within the time interval between two executions, the indicator data calculation does not need to be performed this time, and the process can be terminated directly.

[0168] The solution provided in this embodiment can provide data support for feedback processing such as optimization, backtracking, and failure analysis of drive waveform debugging. Furthermore, providing both real-time and offline calculation methods can adapt to different scenario requirements.

[0169] Corresponding to the driver debugging data storage method provided in the above embodiments of the present invention, such as Figure 7 As shown, this embodiment of the invention also provides a storage system for drive debugging data. The system includes: a data source 701, a data upload module 702, and a data processing module 703. The data source 701 stores debugging data files involved in the drive waveform debugging process of the electronic paper device, wherein:

[0170] The data upload module 702 is used to read the debug data file from the data source 701 and transmit the debug data file to the data processing module 703;

[0171] The data processing module 703 is used to, after receiving the debug data file transmitted by the data upload module 702, parse the debug data file to obtain drive debug data of a specified data dimension; wherein, the specified data dimension is a preset data dimension that needs to be stored among the data dimensions in the debug data file; based on the drive debug data, determine the index data for debugging the drive waveform of the electronic paper device; and store the drive debug data and the index data.

[0172] In the above-described scheme of this invention, drive debugging data of a specified data dimension can be parsed from the debugging data file, and index data for driving waveform debugging of electronic paper devices can be further determined. Then, the drive debugging data and index data are stored, realizing the storage of data during the driving waveform debugging process of electronic paper devices, thereby providing data support for feedback processing such as optimization, backtracking and failure analysis of driving waveform debugging.

[0173] like Figure 8 As shown, this embodiment of the invention also provides another storage system for driver debugging data, the system further including: a display module 704, wherein:

[0174] The display module 704 is used to display the waveform diagram of the driving waveform of the electronic paper device during the debugging process of the driving waveform of the electronic paper device, and / or the data statistics diagram of each indicator data in each debugging stage during the debugging process of the driving waveform of the electronic paper device;

[0175] The waveform diagram is determined based on voltage frame data in a standard frame format and pulse matrix data in a standard pulse format. The voltage frame data in the standard frame format is the data obtained by converting the drive debugging data to a standard frame format when the drive debugging data includes voltage frame data. The pulse matrix data in the standard pulse format is the data obtained by converting the pulse matrix data to a standard pulse format when the drive debugging data includes pulse matrix data. The voltage frame data indicates the voltage value applied by each colored charged particle during the drive waveform debugging process of the electronic paper device. The pulse matrix data indicates the application frequency and cycle information of the voltage applied by each colored charged particle in the voltage frame data. The determination process of the above waveform diagram and / or data statistics diagram has been described in detail in the foregoing embodiments and will not be repeated here.

[0176] The solution provided in this embodiment can provide data support for feedback processing such as optimization, backtracking, and failure analysis in driving waveform debugging. Furthermore, it can display graphical data such as waveform diagrams and data statistics charts, thereby visually displaying the data involved in the driving waveform debugging process of electronic paper devices, and improving the efficiency of data retrieval during the driving waveform debugging process of electronic paper devices.

[0177] like Figure 9As shown in the diagram, this embodiment of the invention also provides a framework diagram of another driver debugging data storage system. The data source includes MySQL, a file database, and a log database. The data upload module provides a data upload service, transmitting debugging data files from the data source to the data processing module. The data processing module monitors in real time whether uploaded debugging data files exist. If they exist, it performs an ETL (Extract-Transform-Load) operation on the uploaded debugging data files to obtain driver debugging data. Then, it performs data preprocessing on the driver debugging data, such as cleaning and verification, and writes the driver debugging data into the data warehouse. Standard driver data, indicator data, and image data are calculated and stored through real-time or offline processing. A query interface service is provided for the stored data, making it convenient for debugging personnel to obtain the required data from the data warehouse. Simultaneously, the data display module can be used to display various types of stored data on the front end, showing various parameters or image data such as waveforms and statistical charts.

[0178] The solution provided in this embodiment can provide data support for feedback processing such as optimization, backtracking, and failure analysis in driving waveform debugging. Furthermore, it can display graphical data such as waveform diagrams and data statistics charts, thereby visually displaying the data involved in the driving waveform debugging process of electronic paper devices, and improving the efficiency of data retrieval during the driving waveform debugging process of electronic paper devices.

[0179] Corresponding to the driver debugging data storage method provided in the above embodiments of the present invention, such as Figure 10 As shown, this embodiment of the invention also provides a storage device for driver debugging data, the device comprising:

[0180] The file acquisition module 1001 is used to acquire the debugging data files involved in the driving waveform debugging process of the electronic paper device;

[0181] The data parsing module 1002 is used to parse the driver debugging data of a specified data dimension from the debugging data file; wherein, the specified data dimension is a preset data dimension that needs to be stored among the data dimensions in the debugging data file;

[0182] The data conversion module 1003 is used to determine the index data for debugging the drive waveform of the electronic paper device based on the drive debugging data;

[0183] The data storage module 1004 is used to store the driver debugging data and the indicator data.

[0184] Optionally, the data storage module is specifically used to convert the drive debugging data into a standard format to obtain standard debugging data; and to use the standard debugging data to determine the index data for debugging the drive waveform of the electronic paper device.

[0185] Optionally, the drive debugging data includes at least one of voltage frame data and pulse matrix data; the voltage frame data indicates the voltage value of each colored charged particle applied by the electronic paper device during the drive waveform debugging process; the pulse matrix data is used to indicate the application frequency and cycle information of the voltage applied by each colored charged particle in the voltage frame data.

[0186] The data storage module is specifically configured to, when the drive debugging data includes the voltage frame data, convert each voltage value in the voltage frame data into a voltage value in a standard voltage format, and / or convert the voltage frame data into voltage frame data in a standard frame format; when the drive debugging data includes the pulse matrix data, convert the pulse matrix data into pulse matrix data in a standard pulse format; and use the converted voltage values ​​in the standard voltage format, the voltage frame data in the standard frame format, and / or the pulse matrix data in the standard pulse format as standard debugging data.

[0187] Optionally, the standard debugging data includes voltage frame data in the standard frame format and pulse matrix data in the standard pulse format; the device further includes:

[0188] The first display module is used to generate a waveform diagram of the driving waveform of the electronic paper device during the debugging process of the electronic paper device driving waveform based on the voltage frame data in the standard frame format and the pulse matrix data in the standard pulse format; and to display the waveform diagram.

[0189] Optionally, the data storage module is specifically used to extract debugging data corresponding to each indicator requirement dimension from the standard debugging data, and calculate the extracted debugging data according to the indicator calculation method corresponding to the indicator requirement dimension, so as to obtain the indicator data under the indicator requirement dimension for debugging the electronic paper device drive waveform.

[0190] Optionally, the data storage module is specifically used to store the driver debugging data, the indicator data, and the standard debugging data in different storage locations.

[0191] Optionally, the device further includes: a data query module, configured to, upon receiving a data query instruction, determine the data to be queried by the data query instruction from the storage locations of the driver debugging data, the indicator data, and / or the standard debugging data; and respond to the data query instruction based on the determined data.

[0192] Optionally, the indicator data includes indicator data from each debugging stage during the debugging process of the electronic paper device drive waveform; the device further includes:

[0193] The second display module is used to generate a data statistics chart of each indicator data in each debugging stage of the electronic paper device driving waveform debugging process after the data conversion module performs the determination of indicator data based on the driving debugging data; and to display the data statistics chart.

[0194] Optionally, the data conversion module is specifically configured to: generate identification information of the driving debugging data as target identification information after the data parsing module executes the step of parsing the driving debugging data of the specified data dimension from the debugging data file, and before determining the indicator data for driving waveform debugging of the electronic paper device based on the driving debugging data; write the target identification information into a message queue; when the target identification information is read from the message queue, execute the step of determining the indicator data for driving waveform debugging of the electronic paper device based on the driving debugging data; and / or, when a preset task execution cycle is reached, execute the step of determining the indicator data for driving waveform debugging of the electronic paper device based on the driving debugging data.

[0195] Optionally, the data parsing module is specifically used to extract data of a specified data dimension from the debug data file as preliminary screening data; and to perform structured data transformation on the preliminary screening data to obtain the transformed data, which is used as the driving debug data of the specified data dimension.

[0196] Optionally, the data parsing module is specifically used to determine preset data labels corresponding to the specified data dimension; and to write the initial screening data into field values ​​with the data labels as field names to obtain the converted data.

[0197] Optionally, the debugging data file includes at least one of a debugging parameter file, a debugging result file, and a debugging standard file; wherein, the debugging parameter file records the waveform parameters of the driving waveform to be applied during the debugging process of the electronic paper device; the debugging result file records the actual display quality data of the electronic paper device after the driving waveform is applied according to the waveform parameters; and the debugging standard file records the standard display quality data that the electronic paper device needs to meet.

[0198] The data parsing module is specifically used to: extract the recorded waveform parameters from the debugging parameter file when the debugging file data includes the debugging parameter file; extract the recorded actual display quality data from the debugging result file when the debugging file data includes the debugging result file; extract the recorded standard display quality data from the debugging standard file when the debugging file data includes the debugging standard file; and use the extracted waveform parameters, actual display quality data, and / or standard display quality data as the initial screening data.

[0199] The solution provided in this embodiment can provide data support for feedback processing such as optimization, backtracking, and failure analysis in driving waveform debugging. Furthermore, it can display graphical data such as waveform diagrams and data statistics charts, thereby visually displaying the data involved in the driving waveform debugging process of electronic paper devices, and improving the efficiency of data retrieval during the driving waveform debugging process of electronic paper devices.

[0200] This invention also provides an electronic device, such as... Figure 11 As shown, it includes a processor 1101, a communication interface 1102, a memory 1103, and a communication bus 1104, wherein the processor 1101, the communication interface 1102, and the memory 1103 communicate with each other through the communication bus 1104.

[0201] Memory 1103 is used to store computer programs;

[0202] When processor 1101 executes the program stored in memory 1103, it performs the following steps:

[0203] Obtain the debugging data files involved in the drive waveform debugging process of the electronic paper device;

[0204] The driver debugging data of a specified data dimension is obtained by parsing the debugging data file; wherein, the specified data dimension is a preset data dimension that needs to be stored among the data dimensions in the debugging data file;

[0205] Based on the drive debugging data, determine the index data for debugging the drive waveform of the electronic paper device;

[0206] The driver debugging data and the indicator data are stored.

[0207] The communication bus mentioned in the above electronic devices can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. This communication bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used to represent it in the diagram, but this does not mean that there is only one bus or one type of bus.

[0208] The communication interface is used for communication between the aforementioned electronic devices and other devices.

[0209] The memory may include random access memory (RAM) or non-volatile memory (NVM), such as at least one disk storage device. Optionally, the memory may also be at least one storage device located remotely from the aforementioned processor.

[0210] The processors mentioned above can be general-purpose processors, including central processing units (CPUs), network processors (NPs), etc.; they can also be 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, or discrete hardware components.

[0211] In another embodiment of the present invention, a computer-readable storage medium is also provided, wherein a computer program is stored therein, and when the computer program is executed by a processor, the steps of any of the above-described methods for storing driver debugging data are implemented.

[0212] In another embodiment of the present invention, a computer program product containing instructions is also provided, which, when run on a computer, causes the computer to execute any of the driver debugging data storage methods described above.

[0213] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present invention are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid state disk (SSD)).

[0214] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0215] The various embodiments in this specification are described in a related manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the system embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

[0216] The above description is merely a preferred embodiment of the present invention and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention are included within the scope of protection of the present invention.

Claims

1. A method for storing driver debugging data, characterized in that, The method includes: Obtain the debugging data files involved in the drive waveform debugging process of the electronic paper device; The driver debugging data of a specified data dimension is obtained by parsing the debugging data file; wherein, the specified data dimension is a preset data dimension that needs to be stored among the data dimensions in the debugging data file; Based on the drive debugging data, determine the index data for debugging the drive waveform of the electronic paper device; The driver debugging data and the indicator data are stored. The drive debugging data includes at least one of voltage frame data and pulse matrix data; the voltage frame data indicates the voltage value of each colored charged particle applied during the drive waveform debugging process of the electronic paper device; the pulse matrix data is used to indicate the application frequency and cycle information of the voltage applied by each colored charged particle in the voltage frame data; the step of determining the index data for drive waveform debugging of the electronic paper device based on the drive debugging data includes: In the case where the drive debugging data includes the voltage frame data, each voltage value in the voltage frame data is converted into a voltage value in a standard voltage format, and / or the voltage frame data is converted into voltage frame data in a standard frame format; If the drive debugging data includes the pulse matrix data, the pulse matrix data is converted into pulse matrix data in a standard pulse format; The converted voltage values ​​in the standard voltage format, the voltage frame data in the standard frame format, and / or the pulse matrix data in the standard pulse format are used as standard debugging data. Using the standard debugging data, the indicator data for debugging the drive waveform of the electronic paper device are determined.

2. The method according to claim 1, characterized in that, The standard debugging data includes voltage frame data in the standard frame format and pulse matrix data in the standard pulse format; The method further includes: Based on the voltage frame data in the standard frame format and the pulse matrix data in the standard pulse format, a waveform diagram of the driving waveform of the electronic paper device during the debugging process of the electronic paper device driving waveform is generated. The waveform diagram is shown.

3. The method according to claim 1, characterized in that, The step of using the standard debugging data to determine the index data for debugging the drive waveform of the electronic paper device includes: For each indicator requirement dimension, the corresponding debugging data is extracted from the standard debugging data, and the extracted debugging data is calculated according to the indicator calculation method corresponding to the indicator requirement dimension to obtain the indicator data under the indicator requirement dimension for debugging the electronic paper device drive waveform.

4. The method according to claim 1, characterized in that, The storage of the driver debugging data and the indicator data includes: The driver debugging data, the indicator data, and the standard debugging data are stored in different storage locations, respectively.

5. The method according to claim 4, characterized in that, The method further includes: When a data query instruction is received, the data to be queried by the data query instruction is determined from the storage locations of the driver debugging data, the indicator data, and / or the standard debugging data; The data query command is responded to based on the determined data.

6. The method according to claim 1, characterized in that, The indicator data includes indicator data in each debugging stage during the debugging process of the electronic paper device drive waveform; After determining the index data for debugging the drive waveform of the electronic paper device based on the drive debugging data, the method further includes: For each debugging stage in the debugging process of the electronic paper device drive waveform, a data statistics chart of each indicator data in that debugging stage is generated; The data statistics chart is displayed.

7. The method according to claim 1, characterized in that, After parsing the driver debugging data of a specified data dimension from the debugging data file, and before determining the indicator data for debugging the electronic paper device's driver waveform based on the driver debugging data, the method further includes: Generate identification information for the driver debugging data as target identification information; write the target identification information into a message queue; when the target identification information is read from the message queue, execute the step of determining the index data for debugging the driver waveform of the electronic paper device based on the driver debugging data; And / or, When the preset task execution cycle is reached, the indicator data for determining the drive waveform debugging of the electronic paper device based on the drive debugging data is executed.

8. The method according to claim 1, characterized in that, The step of parsing the driver debugging data of a specified data dimension from the debugging data file includes: Extract data from the specified data dimensions from the debug data file as initial screening data; The initial screening data is subjected to structured data transformation to obtain the transformed data, which is used as the driving debugging data for the specified data dimension.

9. The method according to claim 8, characterized in that, The process of performing structured data transformation on the initial screening data to obtain transformed data includes: Determine the preset data labels corresponding to the specified data dimension; The initial screening data is written into the field values ​​with the data labels as field names to obtain the transformed data.

10. The method according to claim 8, characterized in that, The debugging data file includes at least one of a debugging parameter file, a debugging result file, and a debugging standard file; wherein, the debugging parameter file records the waveform parameters of the driving waveform to be applied during the debugging process of the electronic paper device; the debugging result file records the actual display quality data of the electronic paper device after the driving waveform is applied according to the waveform parameters; and the debugging standard file records the standard display quality data that the electronic paper device needs to meet. The step of extracting data of a specified dimension from the debug data file as initial screening data includes: If the debug data file includes the debug parameter file, the recorded waveform parameters are extracted from the debug parameter file; If the debug data file includes the debug result file, extract the recorded actual display quality data from the debug result file; If the debug data file includes the debug standard file, extract the recorded standard display quality data from the debug standard file; The extracted waveform parameters, the actual display quality data, and / or the standard display quality data are used as the initial screening data.

11. A storage system for driving debugging data, characterized in that, The system includes: a data source, a data upload module, and a data processing module. The data source stores debugging data files involved in the driving waveform debugging process of the electronic paper device, wherein: The data upload module is used to read the debug data file from the data source and transmit the debug data file to the data processing module; The data processing module is configured to, after receiving the debug data file transmitted by the data upload module, parse the debug data file to obtain drive debug data of a specified data dimension from the debug data file; wherein, the specified data dimension is a preset data dimension that needs to be stored among the data dimensions in the debug data file; based on the drive debug data, determine the index data for debugging the drive waveform of the electronic paper device; and store the drive debug data and the index data. The system also includes: a display module; The display module is used to display the waveform diagram of the driving waveform of the electronic paper device during the debugging process of the driving waveform of the electronic paper device, and / or the data statistics diagram of each indicator data in each debugging stage during the debugging process of the driving waveform of the electronic paper device; The waveform is determined based on voltage frame data in a standard frame format and pulse matrix data in a standard pulse format. The voltage frame data in the standard frame format is the data after converting the drive debugging data to a standard frame format when the drive debugging data includes voltage frame data. The pulse matrix data in the standard pulse format is the data after converting the pulse matrix data to a standard pulse format when the drive debugging data includes pulse matrix data. The voltage frame data indicates the voltage value applied by each colored charged particle during the drive waveform debugging process of the electronic paper device. The pulse matrix data is used to indicate the application frequency and cycle information of the voltage applied by each colored charged particle in the voltage frame data.

12. A storage device for driving debugging data, characterized in that, The device includes: The file acquisition module is used to acquire the debugging data files involved in the driving waveform debugging process of the electronic paper device; The data parsing module is used to parse the driver debugging data of a specified data dimension from the debugging data file; wherein, the specified data dimension is a preset data dimension that needs to be stored among the data dimensions in the debugging data file; The data conversion module is used to determine the index data for debugging the drive waveform of the electronic paper device based on the drive debugging data; A data storage module is used to store the driver debugging data and the indicator data; The drive debugging data includes at least one of voltage frame data and pulse matrix data; the voltage frame data indicates the voltage value of each colored charged particle applied by the electronic paper device during the drive waveform debugging process; the pulse matrix data is used to indicate the application frequency and cycle information of the voltage applied by each colored charged particle in the voltage frame data; The data storage module is specifically configured to: convert each voltage value in the voltage frame data into a standard voltage format voltage value, and / or convert the voltage frame data into a standard frame format voltage frame data, when the drive debugging data includes the voltage frame data; convert the pulse matrix data into a standard pulse format pulse matrix data, when the drive debugging data includes the pulse matrix data; use the converted standard voltage format voltage values, the standard frame format voltage frame data, and / or the standard pulse format pulse matrix data as standard debugging data; and use the standard debugging data to determine the index data for debugging the drive waveform of the electronic paper device.

13. An electronic device, characterized in that, It includes a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus; Memory, used to store computer programs; A processor, when executing a program stored in memory, implements the steps of the method described in any one of claims 1-10.

14. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the steps of the method described in any one of claims 1-10.

Images