Method, device and storage medium for printer system data verification

Abstract

The present invention discloses a method, device, and storage medium for data verification in a printer system. The method includes the following steps: S1, processing an image with RIP software; S2, verifying data; S3, generating SWATH; S4, sending the SWATH to the printer; S5, the printer accepting the SWATH; S6, printing the SWATH; and S7, identifying the printed result and determining abnormal components. The present invention solves the problem that the existing technology cannot better locate abnormal points through the original verification method, and achieves the purpose of all-round detection of printers. The present invention can accurately determine whether the problem is a host computer or a printer based on the printed result, and uses the verification device to further ensure data consistency, thereby improving the reliability of the verification data.

Description

Technical Field

[0001] The present invention relates to the technical field of printers, and in particular to a method, device and storage medium for data verification in a printer system. Background Art

[0002] Currently, factory testing of printer system main control boards only tests each individual board individually, verifying the proper output of the hardware ports and the functionality of individual functions. This doesn't involve assembling all the boards in the printing system for extended testing. This can lead to issues that could have been avoided before the device shipped. Most current methods rely on the sender calculating a checksum based on the data to be sent. The receiver then uses the same calculation method to calculate the checksum and compares it with the sender's checksum. If an error is detected, an alarm is triggered. In practice, the original data sent to the printer may contain a problem. This verification method cannot pinpoint the source of the problem: the data generated by the sender, the transmission process, or the memory allocation on the receiver. This can lead to issues in the printed product, such as garbled images, flickering ink bars, or missing data. Traditional verification methods alone cannot effectively pinpoint the problem; they require a combination of control and data generation methods to better identify the source. Summary of the Invention

[0003] In order to solve the above-mentioned technical problems, the present invention provides a method, device and storage medium for data verification in a printer system.

[0004] The technical solution of the present invention is achieved as follows:

[0005] A method for verifying data in a printer system, comprising the following steps:

[0006] S1, the host computer imports the image into the RIP software, and the RIP software processes the image;

[0007] S2, after processing the image in the RIP software, the print data is sent to the printing module for verification;

[0008] S3, the printing module receives the printing data and generates SWATH, and fills the SWATH with the verified calibration data;

[0009] S4, sending the SWATH filled with calibration data to the printer and storing it in the buffer area;

[0010] S5, determine whether the SWATH in the buffer area is completely received successfully. If so, perform data verification; if not, wait for SWATH to be received successfully. If it is not received successfully within the set time, it is determined that the data transmission is abnormal. If it is necessary to further determine whether the color and line of the printhead are abnormal, proceed to step S9;

[0011] S6, assign all SWATH data to 0 according to the amount N required for a single inkjet of the slice nozzle, and send it to the nozzle for printing;

[0012] S7: The print result is analyzed through image recognition. If no flashing streaks appear, it is determined that the verification data on the host computer is abnormal and the host computer needs to be checked.

[0013] S8: The print result is analyzed through image recognition. If flickering inkjet strips appear, it is determined that the timing logic of the printer transmitting data to the print head is abnormal and needs to be checked.

[0014] Preferably, in step S3, the calibration data for SWATH filling verification includes n slices, and the data filled in the slices are 0X00, 0X01, ... 0X(1+n), and the filling data of each slice is consistent.

[0015] Preferably, in step S4, before sending SWATH, a receive instruction is first sent to the printer, and the receive instruction includes the SWATH inventory. When the printer determines that the SWATH inventory is less than the capacity of the printer buffer area, a confirmation instruction is sent to the host computer. When the printer determines that the SWATH inventory is greater than the capacity of the printer buffer area, the SWATH is divided in the host computer until the printer determines that the SWATH inventory is less than the capacity of the printer buffer area and sends a confirmation instruction to the host computer, and the host computer starts to send SWATH.

[0016] Preferably, in step S5, when the SWATH data is not received successfully within the set time, the host computer is allowed to retransmit the data to the printer, and the number of retransmissions is set to 1-3 times. If the data cannot be successfully received after reaching the maximum number of retransmissions, it is judged as a data transmission abnormality.

[0017] Preferably, in step S5, the data transmission integrity is checked by using a CRC check method, i.e., a cyclic redundancy check method. If the calculated CRC check code is consistent with the received check code, it means that the data is complete; otherwise, it means that the data is incomplete.

[0018] Preferably, in step S5, after the SWATH in the cache area is completely received successfully, the host computer and the printer send the data to the verification machine at the same time, and the verification machine synchronously verifies the data of both. When the verification machine determines that the data is consistent, it proceeds to the next step. When the verification machine determines that the data is abnormal, it is judged that the printer data transmission is abnormal, and the hardware and software modules of the printer data transmission need to be checked.

[0019] Preferably, step S9 is also included, dividing the SWATH data into an upper domain and a lower domain, assigning all N values required for a single inkjet of the slice in the upper domain to 0, and all N values required for a single inkjet of the slice in the lower domain to 1, and sending them to the nozzle for printing.

[0020] Preferably, step S10 is also included, according to the printing result of step S9, the printing result of the upper domain is judged as step S7, the printing result of the lower domain is judged, and the color and lines of the lower domain are judged through image recognition. When the color and lines are abnormal, it is judged that the nozzle is abnormal, and the nozzle hardware structure and nozzle software driver are checked.

[0021] A device for printer system data verification includes at least one processor, at least one memory, and computer program instructions stored in the memory. When the computer program instructions are executed by the processor, the above-mentioned method for obtaining pre-press calibration data for different print heads is implemented.

[0022] A storage medium stores computer program instructions, wherein the computer program instructions are executed by a processor to implement the above-mentioned method for data verification in a printer system.

[0023] The present invention solves the problem that the existing technology cannot better locate abnormal points through the original verification method, and achieves the purpose of all-round detection of printers. In addition, the present invention can accurately determine whether the problem is with the host computer or the printer based on the printing results, and use the verification equipment to further ensure data consistency and improve the reliability of the verification data. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] Figure 1 The diagram is a schematic diagram of a method for data verification applied to a printer system according to the present invention. DETAILED DESCRIPTION

[0025] To further illustrate the technical means and effectiveness of the present invention in achieving its intended purpose, exemplary embodiments will be described in detail herein, with examples illustrated in the accompanying drawings. In the following description, when referring to the drawings, identical numerals in different figures represent identical or similar elements, unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all possible embodiments consistent with the present application. Rather, they are merely examples of methods and systems consistent with certain aspects of the present application, as detailed in the appended claims.

[0026] The terms used in this application are for the purpose of describing specific embodiments only and are not intended to limit this application. As used in this application and the appended claims, the singular forms "a," "an," "the," and "the" are intended to include the plural forms, unless the context clearly indicates otherwise. It should also be understood that the term "and / or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.

[0027] Example 1

[0028] like Figure 1 As shown, the present invention provides a method for data verification in a printer system, comprising the following steps:

[0029] S1, the host computer imports the image into the RIP software, and the RIP software processes the image;

[0030] S2, after processing the image in the RIP software, the print data is sent to the printing module for verification;

[0031] S3, the printing module receives the printing data and generates SWATH, and fills the SWATH with the verified calibration data;

[0032] In step S3, the calibration data for SWATH filling verification is performed. The SWATH data includes n slices, and the data filled in the slices are 0X00, 0X01, ... 0X(1+n). The filling data of each slice is consistent.

[0033] S4, sending the SWATH filled with calibration data to the printer and storing it in the buffer area. In step S4, before sending the SWATH, first send a receive instruction to the printer, and the receive instruction includes the SWATH inventory. When the printer determines that the SWATH inventory is less than the capacity of the printer buffer area, it sends a confirmation instruction to the host computer. When the printer determines that the SWATH inventory is greater than the capacity of the printer buffer area, the SWATH is divided in the host computer until the printer determines that the SWATH inventory is less than the capacity of the printer buffer area and sends a confirmation instruction to the host computer, and the host computer starts sending SWATH.

[0034] S5, determine whether the SWATH in the buffer area is completely received successfully. If so, perform data verification; if not, wait for SWATH to be received successfully. If it is not received successfully within the set time, it is determined that the data transmission is abnormal;

[0035] In step S5, if the SWATH data is not received successfully within the set time, the host computer is allowed to retransmit the data to the printer. The number of retransmissions is set to 1-3 times. If the data cannot be successfully received after the maximum number of retransmissions is reached, it is determined that the data transmission is abnormal.

[0036] In step S5, the data transmission integrity is checked by CRC check method, that is, cyclic redundancy check check method. If the calculated CRC check code is consistent with the received check code, it means that the data is complete. Otherwise, it means that the data is incomplete.

[0037] In step S5, after the SWATH buffer is completely received successfully, the host computer and the printer simultaneously send the data to the verification machine. The verification machine synchronizes and verifies the data of both. When the verification machine determines that the data is consistent, it proceeds to the next step. If the verification machine determines that the data is abnormal, it is determined that the printer data transmission is abnormal and the hardware and software modules of the printer data transmission need to be checked.

[0038] If it is necessary to further determine whether the spray color and lines of the nozzle are abnormal, proceed to step S9; if it is not necessary to further determine whether the spray color and lines of the nozzle are abnormal, proceed to step S6;

[0039] S6, assign all SWATH data to 0 according to the amount N required for a single inkjet of the slice nozzle, and send it to the nozzle for printing;

[0040] S7: The print result is analyzed through image recognition. If no flashing streaks appear, it is determined that the verification data on the host computer is abnormal and the host computer needs to be checked.

[0041] S8: The print result is analyzed through image recognition. If flickering inkjet strips appear, it is determined that the timing logic of the printer transmitting data to the print head is abnormal and needs to be checked.

[0042] Preferably, the step S9 is also included, dividing the SWATH data into an upper domain and a lower domain, assigning all N values required for a single inkjet of the slice in the upper domain to 0, and all N values required for a single inkjet of the slice in the lower domain to 1, and sending them to the nozzle for printing.

[0043] Preferably, step S10 is also included, according to the printing result of step S9, the printing result of the upper domain is judged as step S7, the printing result of the lower domain is judged, and the color and lines of the lower domain are judged through image recognition. When the color and lines are abnormal, it is judged that the nozzle is abnormal, and the nozzle hardware structure and nozzle software driver are checked.

[0044] Preferably, the data assignment is dynamically adjusted based on the feedback information of the nozzle in S6, that is, the actual usage of the amount N required for a single ink jet of the nozzle, obtained through a flow sensor;

[0045] In step S6, during printing, the deviation of the usage of the print head to the data amount N is detected;

[0046] In step S9, when assigning values to the upper and lower domain slices, the assigned data amount is adjusted according to the deviation of the usage of the data amount N by the nozzle. When the actual ink ejection amount of the nozzle is less than the theoretical value, the data amount assigned to the upper and lower domain slices can be appropriately reduced. The adjustment formula is as follows:

[0047] V1=V0*N1 / N2, where V1 is the adjusted assignment amount, V0 is the original assignment amount, N1 is the actual inkjet amount, and N2 is the theoretical inkjet amount. After obtaining V1, V1 is rounded to an integer to better match the actual working conditions of the printhead.

[0048] Preferably, in step S9, the number of slices in the lower domain is set to n, the data of the first slice is: 0x00, 0x01, 0x02, 0x03, the data of the second slice is: 0x04, 0x05, 0x06, 0x07, and so on. The data of the third slice is: 0x08, 0x06, 0x10, 0x11, and the data of the fourth slice is: 0x12, 0x13, 0x14, 0x15. The error slice data is set, and the interval of the error data is m. For every m slices, the data group is: 0x(m+1n), 0x(m+2n), 0x(m+3n), 0x(m+4n). During data verification, for each slice in the lower domain, check whether its data conforms to the sequentially increasing mode, and also need to detect the set error data. When the verification of the error data fails, it is determined that the data transmission between the printer and the nozzle is abnormal.

[0049] It should be noted that the RIP software in the present invention is raster image processing software.

[0050] It should be noted that the data verification method applied to the printer system in the present invention is to perform data verification when the printer has a flashing inkjet problem.

[0051] A device for printer system data verification includes at least one processor, at least one memory, and computer program instructions stored in the memory. When the computer program instructions are executed by the processor, the above-mentioned method for obtaining pre-press calibration data for different print heads is implemented.

[0052] A storage medium stores computer program instructions, wherein the computer program instructions are executed by a processor to implement the above-mentioned method for data verification in a printer system.

[0053] Example 2

[0054] This embodiment is different from the first embodiment and includes the following steps:

[0055] S1, establish the log of the printer and the host computer, determine the log record content, and print task information: including file format, file size, resolution, color mode, and user-set printing parameters.

[0056] Printer status information: printhead temperature, ink level, printhead clogging status, printer operating mode.

[0057] Data verification information: data verification module settings of the host computer and embedded end, as well as verification results.

[0058] S2, record all parameters of the printer flash print results, flash print occurrence time: accurately record the time when the flash print first occurs, and the specific time point of each flash print.

[0059] Flash spray frequency: count the number of flash sprays that occur in a unit of time. You can set different time intervals for statistics, such as the number of flash sprays per minute and the number of flash sprays per hour.

[0060] Flash spray duration: records the time interval from the start to the end of each flash spray, in seconds.

[0061] Flash inkjet position information: For printer heads with positioning function, record the position information of the flash inkjet on the printed page (such as horizontal coordinates and vertical coordinates, in millimeters).

[0062] Combine print tasks and printer status records

[0063] The flash printing result parameters are associated with the current printing task information and printer status information and recorded in the log for subsequent comprehensive analysis.

[0064] S3, check the parameters, compare the parameters of the printer central processing module and the parameters of the nozzle driver module, compare the data verification settings, and check whether the data verification module settings of the host computer and the embedded end are consistent, including whether the verification and filling data modes are turned on. If the settings are inconsistent, it is determined to be a possible software setting error, which affects data transmission and verification, and thus causes flash printing.

[0065] Compare the verification algorithm version numbers. If the host computer and the embedded end use different verification algorithm versions, data verification may not match, and this may be considered an algorithm version inconsistency exception.

[0066] Compare data transmission parameters to check whether the data format and size sent from the host computer to the embedded terminal meet expectations. If the data format does not match, it is judged as a data format error; if the data size differs from the expected value by more than 10%, it is judged as an abnormal data transmission volume.

[0067] Check whether the checksum during data transmission is correct. If the checksum does not match, it is determined that an error occurred during data transmission, which may cause flashing.

[0068] Compare the module working status and whether the working modes of the host computer and the embedded end match. For example, if the host computer is in printing mode, but the embedded end does not correctly identify it as printing mode, it is determined to be an operating mode mismatch exception.

[0069] Check the compatibility of the driver version of the printhead driver module and the printer's central processing unit. If the driver version is too low or too high, it is incompatible with the central processing unit and is considered a driver compatibility anomaly.

[0070] S4, connect the verification machine to the print head driver and repeat the printing parameters in the printer log;

[0071] Verification machine settings: Based on the print task information and printer status information in the printer log, accurately set the relevant parameters on the verification machine, including file format, resolution, color mode, print quality, and paper size.

[0072] Verify the printing process, start the verification printing process of the verification machine, perform the printing operation according to the set parameters, observe the inkjet condition of the print head, and pay special attention to whether there is flashing inkjet.

[0073] S5 identifies the print results from S4 and identifies any flashing issues. If flashing occurs during verification printing, it is determined to be an anomaly in the printhead driver or associated hardware modules. The flashing frequency, duration, and location are further analyzed and compared with the actual flashing behavior of the printer.

[0074] When verifying that no flashing occurs during printing, it is determined that the flashing may be caused by the actual working environment of the printer or other external factors. It is necessary to further check the external factors of the printer's connection line and power supply stability.

[0075] In addition to the flashing phenomenon, print quality inspections also need to check other quality indicators of the print results, such as color accuracy, line clarity, and image integrity. When color deviation exceeds a certain threshold (such as Delta E>5), it is determined to be color accuracy abnormal; when line clarity is lower than the set standard (such as the gradient change of the pixel points at the edge of the line is less than a certain value determined by the edge detection algorithm), it is determined to be line clarity abnormal; when there are missing or blurred areas in the image exceeding a certain proportion (such as more than 10% of the image area), it is determined to be image integrity abnormal.

[0076] S6, analyze the troubleshooting results of S3, and analyze the software setting anomalies. When it is determined that the data verification setting is incorrect or the algorithm version is inconsistent, it is necessary to check the associated settings in the software code to ensure that the data verification settings and algorithm versions of the host computer and the embedded end are consistent.

[0077] For data format errors or abnormal transmission volume, it is necessary to check the data format conversion and transmission control logic in the data processing module to ensure that the data can be transmitted and processed correctly.

[0078] Preferably, in hardware anomaly analysis, when it is determined that the working mode does not match or the driver compatibility is abnormal, it is necessary to check the communication lines and interfaces between the hardware modules to ensure that the working mode can be correctly transmitted and that the driver is compatible with the hardware device.

[0079] If an error occurs during data transmission and cannot be resolved through software settings, it may be caused by a hardware failure, such as a damaged data transmission line or a faulty printhead driver chip. In this case, you need to further check the physical connection and working status of the hardware device.

[0080] Preferably, the various parameters of the printer central processing module and the nozzle driving module are compared one by one, including data verification settings, data transmission parameters, and module working status, and the differences between the two are found through comparison. These differences may be potential causes of printer abnormalities (such as flashing).

[0081] Preferably, the investigation is categorized and the results are categorized into software setting anomalies and hardware-related anomalies. For software setting anomalies, further analysis is performed to determine whether the anomaly is caused by the data verification algorithm, data format, or other software-related settings; for hardware-related anomalies, determination is made whether the anomaly is caused by module compatibility, operating mode mismatch, or hardware failure.

[0082] Preferably, data verification modules are provided for the host computer and the printer, and the data verification modules need to be associated and verified. When the settings of the two are inconsistent, it is determined that the data transmission module of the printer is abnormal.

[0083] Data Verification Principle: During normal data verification, the sender and receiver must use the same verification algorithm and settings to ensure data integrity and accuracy during transmission. If the settings differ, the receiver cannot verify the data as expected by the sender, resulting in misjudgment of data validity, which can affect the printer's normal operation.

[0084] The above description is merely a preferred embodiment of the present invention and does not constitute any form of limitation to the present invention. Although the present invention has been disclosed as above in terms of a preferred embodiment, it is not intended to limit the present invention. Any person skilled in the art can, without departing from the scope of the technical solution of the present invention, make some changes or modifications to equivalent embodiments using the technical contents disclosed above. However, any brief modifications, equivalent changes and modifications made to the above embodiments based on the technical essence of the present invention without departing from the content of the technical solution of the present invention are still within the scope of the technical solution of the present invention.

Claims

1. A method for data verification in a printer system, characterized in that: The steps include: S1, the host computer imports the image into the RIP software, and the RIP software processes the image; S2, after processing the image in the RIP software, the print data is sent to the printing module for verification; S3, the printing module receives the printing data and generates SWATH, and fills the SWATH with the verified calibration data; S4, sending the SWATH filled with calibration data to the printer and storing it in the buffer area; S5, determine whether the SWATH in the buffer area is completely received successfully. If so, perform data verification; if not, wait for SWATH to be received successfully. If it is not received successfully within the set time, it is determined that the data transmission is abnormal; S6, assign all SWATH data to 0 according to the amount N required for a single inkjet of the slice nozzle, and send it to the nozzle for printing; S7, the print result is analyzed through image recognition. If the result shows that no flashing ink bars appear, it is determined that the verification data on the host computer is abnormal. S8, the printing result is analyzed through image recognition. If the result shows a flashing inkjet bar, it is determined that the timing logic of the printer transmitting data to the print head is abnormal; In step S5, after the SWATH in the buffer area is completely received successfully, the host computer and the printer send the data to the verification machine at the same time, and the verification machine synchronizes and verifies the data of both. When the verification machine determines that the data is consistent, it proceeds to the next step. When the verification machine determines that the data is abnormal, it is judged that the printer data transmission is abnormal, and the hardware and software modules of the printer data transmission need to be checked.

2. The method for data verification in a printer system according to claim 1, characterized in that: In step S4, before sending SWATH, a receive instruction is first sent to the printer. The receive instruction includes the SWATH inventory. When the printer determines that the SWATH inventory is less than the capacity of the printer buffer area, a confirmation instruction is sent to the host computer. When the printer determines that the SWATH inventory is greater than the capacity of the printer buffer area, the SWATH is divided in the host computer until the printer determines that the SWATH inventory is less than the capacity of the printer buffer area and sends a confirmation instruction to the host computer. The host computer starts sending SWATH.

3. The method for data verification applied to a printer system according to claim 1, characterized in that: In step S5, if the SWATH data is not received successfully within the set time, the host computer is allowed to retransmit the data to the printer. The number of retransmissions is set to 1-3 times. If the data cannot be received successfully after the maximum number of retransmissions is reached, it is determined that the data transmission is abnormal.

4. The method for data verification in a printer system according to claim 1, wherein: In step S5, the data transmission integrity is checked by CRC check method, that is, cyclic redundancy check check method. If the calculated CRC check code is consistent with the received check code, it means that the data is complete, otherwise it means that the data is incomplete.

5. The method for data verification applied to a printer system according to claim 1, characterized in that: It also includes step S9, dividing the SWATH data into an upper domain and a lower domain, assigning all N values required for a single inkjet of the slice in the upper domain to 0, and all N values required for a single inkjet of the slice in the lower domain to 1, and sending them to the nozzle for printing.

6. The method for data verification in a printer system according to claim 1, characterized in that: It also includes step S10, judging the printing result of the upper domain as in step S7 according to the printing result of step S9, judging the printing result of the lower domain, and judging the color and lines of the lower domain through image recognition. When the color and lines are abnormal, it is judged that the nozzle is abnormal, and the nozzle hardware structure and nozzle software driver are checked.

7. A device for data verification in a printer system, comprising at least one processor, at least one memory, and computer program instructions stored in the memory, wherein when the computer program instructions are executed by the processor, the method according to any one of claims 1 to 6 is implemented.

8. A storage medium having computer program instructions stored thereon, characterized in that: When the computer program instructions are executed by a processor, the method according to any one of claims 1 to 6 is implemented.

Images