Inspection device, control method for inspection device

Abstract

To solve the problem that when setting inspection areas for inspecting matching of front and back faces, the inspection areas have to be set on the front face and the back face respectively, which puts a great burden on an operator.SOLUTION: An inspection apparatus has: area setting means that sets a first area in which a matching inspection is performed to a received reference image; generating means that when receiving an instruction for the matching inspection, generates a second area having the same setting as the first area set by the area setting means; extracting means that extracts data from the first area and the second area, with respect to a read image obtained by reading, by reading means, a printed matter having an image formed thereon by image forming means; and inspecting means that inspects whether or not data extracted from the first area by the extracting means matches data extracted from the second area by the extracting means.SELECTED DRAWING: Figure 7

Description

Technical Field

[0001] The present invention relates to an inspection device and a method for controlling the inspection device.

Background Art

[0002] Conventionally, inspection (product inspection) to check whether printed matter is correctly printed has been performed manually. In recent years, however, a device that automatically performs product inspection as a post-processing of a printing machine has been used. In such an inspection device, inspection is performed on variable area portions (variable data) such as character strings and barcodes in variable printing. For example, there are a data readability inspection for checking whether a character string or barcode can be read, and a data collation inspection for collating the read result of a character string or barcode with a correct answer. Hereinafter, the data readability inspection and the data collation inspection are referred to as data inspection. In addition, one of the data inspections is a matching inspection.

[0003] In Patent Document 1, a method for front-back matching inspection for checking whether the read results of data inspection areas set on the front and back surfaces match has been proposed.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] However, in the method of Patent Document 1, when setting the inspection area for the matching inspection, inspection areas must be set on each of the front and back surfaces, so there is a problem that a large load is imposed on the operator in setting the matching inspection.

Means for Solving the Problems

[0006] The inspection device of the present invention isReference image RAM as a storage means for storing the above Reference image The system has a CPU as a control means that performs inspection of the scanned image of the printed material based on the inspection settings, and the control means has a CPU as the inspection settings, Operator Operation Therefore, it matches inspection Data inspection settings used and in the aforementioned matching test Examination area This becomes the first region. and to the above Reference image Set for, and, Operator By receiving instructions for matching from the first region, the same Data Inspection Settings The second region having the above Reference image The system is configured to automatically perform the inspection, and in the inspection, it extracts data from the regions corresponding to the first region and the second region from the read image, and checks whether the data extracted from the first region matches the data extracted from the second region. [Effects of the Invention]

[0007] According to the present invention, the burden of setting the back surface when setting the area for matching inspection can be greatly reduced. [Brief explanation of the drawing]

[0008] [Figure 1] An example diagram showing an example of a system configuration including the inspection device of this embodiment. [Figure 2] An example of an internal configuration diagram of the image forming apparatus 100 in this embodiment. [Figure 3] An example of an internal configuration diagram of the inspection device 110 in this embodiment. [Figure 4] An example of a flowchart of the entire inspection process in this embodiment [Figure 5] An example of a UI screen for job management in this embodiment [Figure 6] An example of a UI screen for inspection settings in this embodiment [Figure 7] Example of a flowchart for the inspection settings (S403) in Embodiment 1 [Figure 8]An example of the display of the matching check area in Embodiment 1 [Figure 9] An example of the flowchart of the generation of the matching check area (S705) in Embodiment 2 [Figure 10] An example of the setting of the matching check area in Embodiment 2 [Figure 11] An example of the flowchart of the generation of the matching check area (S705) in Embodiment 3 [Figure 12] An example of the UI at the time of generating the matching check area (S705) in Embodiment 4 [Figure 13] An example of the UI at the time of generating the matching check area (S705) in Embodiment 5

Modes for Carrying Out the Invention

[0009] Each embodiment of the present invention will be described in detail with reference to the accompanying drawings. Note that the following embodiments do not limit the invention according to the claims, and not all combinations of the features described in each embodiment are essential for the solution means of the present invention.

[0010] In the following description, the image forming apparatus may also be called a multifunction printer, a multi-function peripheral, or an MFP (Multi Function Peripheral).

[0011] <Embodiment 1> FIG. 1 is a diagram showing a system configuration including an inspection apparatus according to an embodiment of the present invention. 100 is an image forming apparatus, 110 is an inspection apparatus, 120 is a finisher, 130 is a client PC, 140 is a print server, and 150 is a network.

[0012] The image forming apparatus 100 performs print output based on various input data, for example, print data sent from the client PC 130 or the print server 140. In the present embodiment, it is described as an image forming apparatus, but it is not limited thereto, and any apparatus that prints on a recording medium may be used. For example, an apparatus that prints on metal may also be used.

[0013] The inspection device 110 inspects the printed materials that are sequentially transported from the image forming apparatus 100 to determine whether or not they have defects. A defect here refers to anything that degrades the quality of the printed material, such as stains caused by colorants adhering to unintended areas during printing, or color fading caused by insufficient colorants adhering to intended areas.

[0014] Furthermore, the inspection device 110 inspects variable areas in variable printing that include variable areas such as one-dimensional codes like strings and barcodes, and two-dimensional codes like QR codes (registered trademark). For example, it performs data readability checks to see if strings or barcodes are readable, and data matching checks to compare the reading results of strings or barcodes with the correct answer. In addition, it performs front-back matching checks to see if the reading results of the data inspection areas set on the front and back sides match. In other words, the inspection device 110 performs print image inspections to detect abnormalities in the image portion of the printed material, as well as data inspections including data readability checks and data matching checks. It should be noted that the inspection processing unit that performs print image inspections and data inspections does not necessarily need to be located inside the inspection device 110; for example, the inspection processing may be performed by an information processing device (not shown) acting as an inspection PC that is communicably connected to the inspection device 110. In this embodiment, barcode inspection refers to inspections that can also inspect two-dimensional codes such as QR codes. Furthermore, the inspection system in this embodiment consists of at least an inspection device 110 that inspects printed materials.

[0015] The finisher 120 receives the output paper inspected by the inspection device 110, switches the output destination based on the inspection results of the inspection device 110, performs post-processing (such as binding and stapling) as necessary, and then outputs the paper.

[0016] The image forming apparatus 100 is connected to client PCs 130 and print servers 140 via a network 150, and further connected to inspection apparatus 110 and finisher 120 via communication cables. The inspection apparatus 110 is connected to the finisher 120 as well as the image forming apparatus 100 via communication cables. This embodiment will be explained using an inline inspection machine that performs image forming, inspection, post-processing, and paper discharge in an integrated manner as an example, but there is no intention to limit the present invention.

[0017] [Configuration diagram of an image forming apparatus] Figure 2 shows the internal configuration of the image forming apparatus 100 in this embodiment. The controller 200 receives images and documents from the network 150 and converts the received images and documents into print data. The printer unit 210 generates printed materials by printing the print data onto a recording sheet (paper, sheet). The UI unit 220 displays information on the screen and receives instructions from the operator to the image forming apparatus 100, such as the selection of paper information. The image forming apparatus 100 consists of the controller 200, printer unit 210, and UI unit 220 described above.

[0018] Components 201-208 are part of the controller 200. The network interface unit 201 sends and receives data to and from the client PC 130 and print server 140 via the network 150. The CPU 202 controls the entire image forming apparatus 100.

[0019] RAM203 is the work area where the CPU202 executes various instructions, and ROM204 stores program data executed by the CPU202 at startup, controller200 configuration data, etc. The image processing unit205 performs RIP (Raster Image Processor) processing to convert image and document data received from network150 into print data.

[0020] In this embodiment, it is not necessary for the RIP processing to be performed in the image processing unit 205. For example, the RIP processing may be performed in an information processing device (not shown) that is communicatively connected to the image forming apparatus 100.

[0021] The engine interface unit 206 transmits print data to the printer unit 210. The communication interface unit 207 communicates with the inspection device 110 and the finisher 120. 208 is the internal bus (system bus).

[0022] Images and documents created on a client PC 130 or print server 140 on network 150 are transmitted as PDL data to the image forming apparatus 100 via the network (e.g., Local Area Network). Alternatively, print jobs such as images and documents may be transmitted via the network to an information processing device (not shown) and managed by the information processing device. The print jobs may then be transmitted from the information processing device to the image forming apparatus 100 via network 150, and the image forming apparatus 100 may perform the printing process on paper.

[0023] The transmitted PDL data is stored in RAM 203 via the network I / F unit 201. Additionally, print instructions from the UI unit 220 are also stored in RAM 203 via the internal bus 208. These operator print instructions include, for example, the selection of paper type.

[0024] The image processing unit 205 acquires the PDL data stored in the RAM 203 and performs image processing to convert it into print data. Image processing to convert to print data includes, for example, rasterizing the PDL data to convert it into multi-level bitmap data, and then performing screen processing to convert it into binary bitmap data. The binary bitmap data obtained by the image processing unit 205 is transmitted to the printer unit 210 via the engine I / F unit 206.

[0025] The printer unit 210 prints the received binary bitmap data onto a recording sheet using colorants. The CPU 202 issues instructions to the printer unit 210 based on the operator's print instructions stored in the RAM 203. For example, if the operator instructs to print on coated paper, the CPU 202 instructs the printer unit 210 to output paper from a paper cassette (not shown) in the image forming apparatus 100 where coated paper is stored. The various processes from the reception of the PDL data to printing on the paper are controlled by the CPU 202, so that a full-color toner image is formed on the paper.

[0026] [Internal configuration of inspection device 110] Figure 3 shows the internal configuration of the inspection device 110. The inspection control unit 300 controls the entire inspection device 110 and the inspection process to determine whether or not there are defects in the printed material.

[0027] The image reading unit 310 reads the printed material transported from the image forming apparatus 100. The image reading unit 310 generates a scanned image (read sheet) by reading the printed material.

[0028] The UI unit 320 is a user interface (UI) unit for the operator to configure the inspection device 110 and display inspection results to the operator. Here, the configuration of the inspection device 110 performed by the operator refers to the items of defects to be inspected when inspecting printed materials. Inspection items include, for example, round defects (dots) and linear defects (streaks). The inspection device 110 consists of the inspection control unit 300, the image reading unit 310, and the UI unit 320 described above. In this embodiment, the UI unit 320 consists of a display unit that displays the screen and a display control unit that controls the screen displayed on the display unit. Furthermore, the configuration of the inspection device 110 and the display of inspection results performed by the UI unit 320 may be configured to receive display and instructions from external devices such as the UI unit 220 of the image forming apparatus 100, an inspection PC (not shown), or an information processing device (not shown).

[0029] Components 301-306 are part of the inspection control unit 300. The communication interface unit 301 transmits and receives data with the image forming apparatus 100, finisher 120, and inserter 160. The CPU 302 controls the entire inspection apparatus 110. The RAM 303 is the work area where the CPU 302 executes various instructions, and the ROM 304 stores program data executed by the CPU 302 at startup, as well as setting data for the inspection control unit 300. The correct answer CSV file, described later, is also stored in the ROM 304. The inspection processing unit 305 inspects whether or not there are defects in the printed material. The internal bus 306 is the system bus.

[0030] (Print image inspection) The following describes the print image inspection performed by the inspection device 110. The inspection device 110 reads the printed material transported from the image forming apparatus 100 using the image reading unit 310 and acquires a scanned image (read image) of the object to be inspected. The acquired scanned image of the object to be inspected is stored in the RAM 303. Next, the inspection device 110, using the inspection processing unit 305, acquires a difference value between the scanned image of the object to be inspected and a reference image that has been previously stored in the RAM 303 as a correct image.

[0031] Next, the inspection device 110 performs the inspection by comparing the calculated difference value with the inspection threshold (such as contrast or size) for each inspection item for each pixel. The results of the inspection are stored in the RAM 303, which stores information such as whether or not there is an abnormality in the printed material, the type of abnormality detected (such as a dot or streak), and the location information of the abnormality when displayed on the UI unit 320.

[0032] (Data analysis) This section describes the overview of the data inspection performed by the inspection device 110. The inspection device 110 reads printed materials sequentially transported from the image forming apparatus 100 using the image reading unit 310 and acquires scanned images of the items to be inspected. The acquired scanned images of the items to be inspected are stored in the RAM 303. Next, the inspection processing unit 305 of the inspection device 110 first performs an extraction process to extract data from strings, barcodes, and QR codes within the scanned images. This is done using pre-set glyph fonts for optical character recognition (OCR) and barcode standards, with OCR processing performed for characters and decoding processing performed for barcodes. In the data inspection, the device checks whether the strings and barcodes within the area set for data inspection are readable. If they are readable, an OK judgment is made; if they are not readable, an NG judgment is made. It is also possible to perform a data matching inspection to check whether the extracted data, such as the read strings and barcodes, matches the corresponding data (correct data) in a pre-prepared correct answer CSV file. Here again, if the matching results in data matching, an OK judgment is made; if they do not match, an NG judgment is made. The results of the inspection are stored in RAM303, which includes, for example, the results of reading strings and barcodes from printed materials, the results of comparison with correct data, and the position information of the read characters and barcodes when displayed on UI unit 320.

[0033] (Checking for consistency between front and back) This section describes the overview of the front-to-back matching inspection performed by the inspection device 110. Similar to data inspection, the inspection device 110 reads the printed material and performs extraction processing to extract data from the text strings, barcodes, and QR codes within the scanned image. In the front-to-back matching inspection, it determines whether the data extracted from the front side matches the data extracted from the back side. If they match, it is judged as OK; if they do not match, it is judged as NG. The results of the inspection are stored in the RAM 303, for example, the results of the text strings and barcodes read from the printed material, the results of the front-to-back matching / non-matching, and the position information of the read characters and barcodes when displayed on the UI unit 320.

[0034] After the completion of the print image inspection, data inspection, and front-to-back matching inspection described above, the inspection device 110 instructs the UI unit 320 via the CPU 302 to display the inspection results stored in the RAM 303. The operator recognizes the inspection results when they are displayed on the UI unit 320. Furthermore, if a defective print is generated, or if a certain quantity of defective prints are generated consecutively, the inspection device 110 transmits the above information via the communication I / F unit 301 via the CPU 302.

[0035] The controller 200 receives information that a defective printout has been produced via the communication interface unit 207. Upon receiving this information, the CPU 202 instructs the printer unit 210 to stop printing. The image forming apparatus 100 stops printing when the printer unit 210 is instructed to stop printing.

[0036] Furthermore, the inspection device 110, based on the inspection results stored in the RAM 303 via the CPU 302, also transmits information to the finisher 120 via the communication I / F unit 301. The information transmitted to the finisher 120 is whether or not the printed material has defects. Using the received information, the finisher 120 ejects printed materials without defects to the normal output tray and printed materials with defects to a tray separate from the normal output tray.

[0037] <Overall Inspection Flow> Next, the overall flow from the registration process before the start of inspection to the execution of inspection in the inspection device 110 will be explained using the flowchart in Figure 4. This flowchart is realized when the CPU 302 loads the program code stored in the ROM 304 into the RAM 303, and then reads and executes the program code loaded into the RAM.

[0038] In step S401, the CPU 302 registers a glyph font. The glyph font registered here is used during data inspection. A glyph font is data that associates glyph images and character codes of characters necessary for optical character recognition (OCR) performed during data inspection. The procedure for creating a glyph font is as follows: First, the inspection device 110 waits in glyph font image reading mode and receives a print job for glyph font creation from the client PC 130. The inspection device 110 receives the glyph font job from the client PC 130 and reads the glyph font image. When printing is executed, the inspection device 110 detects the transport of the printed material from the image forming apparatus 100, scans the printed material with the image reading unit 310, and saves the scanned image to the RAM 303 of the inspection device 110. From the scanned image, the characters to be OCR are extracted one by one, and the operator inputs the character code for the extracted character image to create a glyph font. The created glyph font is saved to the RAM 303 of the inspection device 110. This document describes the method for creating character fonts in this embodiment, but it is not limited to this method; any method that can create data by associating character codes with each character image extracted from a scanned image is acceptable. It is also possible to perform only print image inspection without data inspection. In this case, S401 is skipped and the process proceeds to S402.

[0039] In step S402, the CPU 302 registers a reference image that will be the correct image for inspection. The inspection device 110 waits in reference image reading mode, and a print job for reference image registration is executed from the client PC 130. When printing is executed, the inspection device 110 detects the transport of the printed material, scans the printed material with the image reading unit 310, and the scanned image is saved as the reference image in the RAM 303 of the inspection device 110. In this embodiment, the reference image is registered by scanning it with the image reading unit 310, but this is not the only method. For example, the print server 140 or an image processed by the image processing unit 205 of the image forming apparatus 100 may be registered as the reference image.

[0040] In step S403, the CPU 302 receives the inspection settings and stores various inspection setting values ​​such as the inspection area and inspection level in the RAM 303 of the inspection device 110. Details of S403 in this embodiment will be described later.

[0041] In step S404, the CPU 302 receives a print job for inspection from the client PC 130, detects the paper transport, scans the paper with the image reading unit 310, and saves the scanned image to the RAM 303 of the inspection device 110. Then, the CPU 302 performs a pattern inspection using the scanned image of the inspection job and the reference image registered in S402, along with the inspection settings set in S403. In addition, a data inspection is performed using the glyph font registered in step S401 and the inspection settings set in step S403. This completes the processing of this flowchart.

[0042] Figure 5 shows an example of the job management screen 500 displayed on the UI unit 320.

[0043] The job management screen 500 is displayed when the inspection device 110 is started. Alternatively, it is displayed when an application is launched by an operator via the UI unit 320.

[0044] From the job management screen 500, it is possible to transition to each of the following processes: font registration, reference image registration, inspection settings, and inspection.

[0045] Button 501 is used to clear the display on screen 500. Button 502 is used to create a new inspection job and register a reference image.

[0046] Button 503 is used to duplicate an already created inspection job. It duplicates the inspection job selected in the inspection job list 508. By duplicating the job, the reference image and inspection settings are duplicated, and a new inspection can be performed. Pressing button 503 will take you to the inspection settings screen shown in Figure 6.

[0047] Button 504 is the delete button, which deletes the inspection job selected in the inspection job list 508. Multiple inspection jobs can be selected and button 504 pressed to delete them simultaneously. Button 505 is the inspection settings button, which configures the inspection settings for inspection jobs for which reference image registration has been completed.

[0048] Button 506 is an inspection button that performs inspection on inspection jobs for which reference image registration and inspection settings have been completed. Button 507 is a font registration button that registers glyph fonts.

[0049] [Test settings] Next, the inspection settings will be explained using Figure 6. Figure 6(a) is an example of the inspection setting screen 600 displayed on the UI section 320 of the inspection device 110 for performing inspection settings.

[0050] Button 601 is the reference image change button, used when changing the reference image. Button 602 is the inspection area selection button, pressed by the operator when they want to select an already set area.

[0051] Button 603 is the delete button for the inspection area, and is pressed by the operator when they want to delete the selected area. Button 604 is for rotating the image displayed in area 605.

[0052] Area 605 is the display area for displaying the loaded reference images. If there are multiple sheets to load, the displayed image is switched using button 610. The front and back of the loaded sheets are also switched using button 610. Specifically, each time the right arrow button 610 is pressed, the display switches in the following order: front of sheet 1, back of sheet 1, front of sheet 2, back of sheet 2.

[0053] Button 611 is an OK button that saves the settings on screen 600 and transitions to the job management screen 500 shown in Figure 5. Alternatively, pressing button 611 may transition to an inspection screen (not shown) and allow the inspection to be executed. Button 612 is a Cancel button that does not save the settings on screen 600 and transitions to the job management screen 500 shown in Figure 5.

[0054] Button 621 is pressed by the operator when creating a new print image inspection area. After pressing the button, the operator sets the inspection area for the reference image displayed in area 605. Area 606 shows an example of setting a print image inspection area.

[0055] Button 622 is pressed by the operator when creating a new area for character inspection or barcode inspection. After pressing the button, the operator sets the inspection area on the reference image displayed in area 605. Area 607 shows an example of setting a character inspection area. Area 608 shows an example of setting a barcode inspection area. In Figure 6, areas 606, 607, and 608 are shown with the same black dotted line, but they may be displayed in a way that makes it clear that they are areas where different processes are performed. For example, the border colors of areas where different processes are performed could be displayed with different colors or dashed lines. The operator may also be able to select the display color of these borders.

[0056] Button 623 is pressed by the operator when creating a new sequential numbering inspection area. After pressing the button, the operator sets the inspection area for the reference image displayed in area 605. Sequential numbering inspection performs data inspection based on predetermined rules. These rules include the start number, end number, increment / decrement value, etc.

[0057] Setting item 631 is for positional misalignment inspection, and sets the acceptable amount of misalignment of the print position from the reference image. In this embodiment, an example is shown where the operator specifies the value when detecting a misalignment of 2 mm or more. In other words, the value specified by the operator here corresponds to the threshold for positional misalignment detection. If a misalignment exceeding the threshold set here is detected, the inspection is judged as NG (Not Resulting).

[0058] The settings area 632 is a group of UI elements for configuring the currently selected area in area 605. The settings item 633 sets the scope of application for the selected area. If nothing is selected, the selected inspection area will only be placed on the page currently displayed in area 605. If "Same side as current page" is selected, the selected inspection area will be placed on pages on the same side as the sheet, depending on whether the selected inspection area is located on the front or back of the sheet. If "All pages" is selected, the selected inspection area will be placed on all pages.

[0059] Setting item 634 is for setting round defects (dots) and linear defects (streaks), and sets the detection level for each. The detection level is a parameter set in stages to determine how large a defect must be to be considered a defect, depending on the characteristics of the detected defect. For example, there are five levels from level 1 to level 5, and level 5 can detect thinner and smaller defects than level 1. Also, a level can be set for each inspection item, such as inspection level 5 for dots and inspection level 4 for streaks. Setting item 634 indicates that the operator has selected inspection level 4 for both defects (dots) and defects (streaks).

[0060] Figure 6(b) shows an example of the inspection settings screen when the currently selected setting area is the data area. Setting area 641 is a group of UI elements for configuring the data inspection area, which is displayed when the data inspection area is selected in area 605.

[0061] This explanation assumes that character area 607 is currently selected, but the same settings should be applied to character area 609. Note that in area 605, the selected area is clearly distinguishable from the unselected areas.

[0062] The setting area 642 sets the scope of application for the selected area. If nothing is selected, the selected inspection area will only be placed on the page currently displayed in area 605. If "Same side as current page" is selected, the selected inspection area will be placed on the same side of the sheet, depending on whether the selected inspection area is located on the front or back of the sheet. If "All pages" is selected, the selected inspection area will be placed on all pages.

[0063] Setting area 643 is where you set the correct CSV file to be used for matching during the matching check. Pressing button 644 allows you to select a file, and the selected file name will be displayed. The specification of the correct CSV file is common to both character checks and barcode checks. Setting area 645 is where you configure the currently selected data check area. Here you can set the orientation, select whether to check the character area or the barcode area, the font type, the barcode type, whether to perform a matching check, and specify the columns of the correct CSV file for the matching check. These settings necessary for data checks are called check parameters.

[0064] Setting item 646 sets the orientation of the characters in character area 607. Setting items 647 and 648 specify whether the selected area is for text character inspection or barcode inspection. Setting item 649 sets the font for OCR processing of character area 607. Setting item 650 sets the barcode type if barcode inspection is selected in setting item 648.

[0065] Setting item 651 is used to specify whether or not to perform a matching check. If matching check is set to "Yes", the OCR process of the character area 607 is performed using the correct answer CSV file specified in setting area 643 and the column number specified in setting item 652, and a matching check is performed between the read string and the string specified in the correct answer CSV.

[0066] Setting item 653 is used to determine whether or not to perform a match check. A match check is a test to determine whether the reading results of two or more inspection areas match. For example, a match check area (not shown) is set on the opposite side from the currently selected character area 607, and the system checks whether the reading results of the areas on the front and back sides match. In particular, performing a match check between an object on the front and an object on the back side may be called a front-to-back check or front-to-back match check.

[0067] Here, data inspection is given as an example of data readability inspection, which checks whether text or barcodes are readable; data matching inspection, which compares the read results of text or barcodes with the correct answer; and front-to-back matching inspection, which checks whether the read results on the front and back match. However, it is not limited to these. For example, it could also be a sequential numbering inspection, which checks whether the read results are sequential numbers, or a matching inspection, which checks whether the read results at multiple locations on a surface match. Any inspection that reads text or barcodes is acceptable.

[0068] <Inspection Setup Flow> Next, the flow of the inspection settings for S403 will be explained using the flowchart in Figure 7. This flowchart is realized when the CPU 302 of the inspection device 110 loads the program code stored in ROM 304 into RAM 303, and then reads and executes the program code loaded into RAM 303.

[0069] In step S701, the CPU 302 receives notification of the operator's UI operation from the UI unit 320.

[0070] In step S702, the CPU 302 determines whether or not a check setting has been performed. Specifically, it determines whether a new data check area has been created or whether the settings of an already created data check area have been changed. If a check setting has been performed (YES in step S702), the process proceeds to step S703. If the operation is anything other than a check setting (NO in step S702), the process proceeds to step S707.

[0071] In step S703, the CPU 302 determines whether a match check is set in the inspection settings of step S702. If a match check is set (YES in step S703), proceed to step S704. If a match check is not set (NO in step S703), proceed to step S707.

[0072] In step S704, the CPU 302 determines whether a matching check area has already been created. The matching check area refers to the area where a matching check is performed with the data check area set in step S702. If a new data check area has been created, the matching check area has not yet been created (YES in step S703), so the process proceeds to step S705. If the data check area setting has been changed, the matching check area has already been created (NO in step S703), so the process proceeds to step S706.

[0073] In step S705, the CPU 302 generates a matching inspection area for the data inspection area set in step S702. The matching inspection area generated here is set with the same inspection settings, such as orientation and character type, as set for the selected inspection area. The matching inspection area generated here may be generated on the same page as the sheet in which the data inspection area was set in S702, or on a different page. Alternatively, it may be generated on a different page of the same sheet.

[0074] In step S706, the CPU302 accepts the operator's request to change the inspection area settings. When changing the matching inspection area settings, there may be restrictions on the items that can be changed, and confirmation may be required when making changes, but details will be described later.

[0075] The generation of the matching inspection area will be explained in detail using Figure 8. Figure 8(a) shows area 605 when the data inspection area is set in step S702. Image 801 is a reference image, and the QR code in the image is set as the data inspection area 802. "Set" means that all the required items for setting area 641 in Figure 6(b) have been set. Required items are, for example, for data readability inspection, the orientation, selection of the character area or barcode inspection area, font type, and barcode type. For data matching inspection, the orientation, selection of the character area or barcode inspection area, font type, barcode type, whether or not to perform matching inspection, and the column of the correct CSV file during matching inspection. When enabling matching inspection for data inspection area 802, it is desirable that the required items of the above settings have been set. This is because the settings of the data inspection area are inherited when the matching inspection area is automatically generated, thereby reducing the setting burden on the operator. Therefore, the matching inspection setting item 653 is grayed out until the required items for data inspection area 802 have been set. Alternatively, a warning could be issued if setting item 653 for matching checks is enabled when the required fields are not set.

[0076] Figure 8(b) shows area 605 when the matching inspection area is set in step S705. Image 803, displayed alongside image 801, is the reverse side of image 801 and has the same QR code as image 801. When data inspection area 802 is selected and matching inspection is set, CPU 302 generates and displays matching inspection area 804. At this time, the selected area shifts from data inspection area 802 to matching inspection area 804. The settings of matching inspection area 804 are the same as those of data inspection area 802 except that it is located on the reverse side of data inspection area 802. Therefore, at the time matching inspection area 804 is generated, the position of the QR code in matching inspection area 804 does not match that of image 803. At this point, the operator changes the settings of matching inspection area 804.

[0077] In this embodiment, as shown in Figure 8(b), the images of the front and back surfaces may be displayed side by side in area 605. The display of the front and back surfaces side by side may be switched by pressing a display method switching button (not shown), or it may be configured to be switched by pressing the matching inspection setting item 653.

[0078] Figure 8(c) shows the matching inspection area 805 after the settings have been changed. The setting change here is a change in the position of the matching inspection area 804. The method of changing the position can be any method that allows the operator to appropriately change the inspection area settings, such as the operator dragging and dropping the matching inspection area 804 or the operator re-selecting the location of the QR code. Other settings related to data inspection can also be changed by the operator as needed. However, if data matching inspection is set for the data inspection area 802, it may be possible to notify the operator that the settings for the correct CSV file in setting area 643, whether or not to perform matching inspection in setting area 651, and the column number in setting area 652 will not be accepted. As a method of prohibiting setting changes, it is sufficient to notify the operator that the settings cannot be changed, such as graying out the items for which setting changes will not be accepted, or issuing a warning when a setting is changed.

[0079] Even when changing the inspection settings after the matching inspection area has been set once, CPU302 will display the front and back images side by side as shown in Figure 8(c) to allow changes to the inspection settings. When the settings of data inspection area 802 are changed, whether to apply the setting change to matching inspection area 805 will be confirmed by a pop-up on the UI each time a setting change is made, or this can be predetermined in the initial settings. Also, in Figure 8(b), data inspection area 802 and matching inspection areas 804 and 805 are shown with the same black dashed line. For example, automatically generated matching inspection areas 804 and 805 may be displayed with different line colors, shapes, thicknesses, and actions than data inspection area 802, and then displayed the same as data inspection area 802 after the settings are complete. Note that if you want to perform matching checks in two places, such as text and QR codes, as shown in Figure 8(d), you can specify data inspection area 802, then specify matching checks, and then generate data inspection area 805. Furthermore, by specifying a data inspection area 806 and then specifying a match check, it is possible to specify two match checks on a single sheet by generating a data inspection area 807.

[0080] Next, in step S707, the CPU 302 determines whether the inspection area settings have been completed. Here, the determination is made based on whether the button (OK button) 611 shown in Figure 6(a) has been pressed. If button 611 is pressed (YES in step S707), the CPU 302 determines that the inspection settings have been completed, saves the settings set on the inspection settings screen to RAM 303, and terminates the inspection settings process. If the OK button has not been pressed (NO in step S707), the process returns to step S701, and the CPU 302 waits for notification of UI operation. This concludes the explanation of the inspection settings flow in step S403.

[0081] [Concordance test] We have explained the setup flow for matching tests so far, but now we will explain the content of the matching test and how it is displayed.

[0082] As mentioned above, matching checks are one type of data check, and they check whether the data matches. Therefore, the data does not need to be displayed in the same format, and it can be strings of text or strings and barcodes, as long as the results read as data match.

[0083] There are several possible methods for matching checks. Here, if matching checks are set for data A and data B in a given print data set, the checks described below will be performed on data A and data B respectively. First, we will explain the case where only the read results of the areas where matching checks are set match. The CPU 302 sequentially saves the read results of all areas where matching checks are set to RAM 303, compares the saved read results, and determines which data matches and which does not. If even one piece of data does not match, the matching check fails.

[0084] Next, we will explain the case where all matching check areas check the same CSV data as the correct answer. The CPU 302 sequentially saves the results of the data matching checks for all areas where matching checks are set to RAM 303 and determines whether there are any NGs. If even one NG is found, the matching check is considered NG.

[0085] Furthermore, we will explain the case where data matching is performed on only one matching check area, and the other matching check areas are checked to see if the read results match those of the checked check area. CPU 302 saves the results of the data matching check and the read results of all matching check areas, and compares the saved read results to determine which data matches and which does not. If the data matching check fails or if there is even one data that does not match, the matching check fails.

[0086] An example of how to display the matching inspection area is shown using Figure 8(d). In Figure 8(d), matching inspection for data A and matching inspection for data B are shown as an example where matching inspection for two data sets is set on both the front and back sides of the printed document.

[0087] Characters 806 and 807 are targets for matching, separate from data A displayed by the QR codes in the aforementioned check areas 802 and 805. Icons 808 and 809 are icons added to the matching check areas. Adding the same icon to matching check areas makes it easier to recognize areas that are being matched. Also, when multiple matching check areas are set on a page, they can be distinguished by changing the numbers on the icons. The method of displaying matching check areas is not limited to this; any method that makes areas being matched easily recognizable and distinguishable is acceptable, such as adding a mark, changing the pattern, thickness, or color of the border.

[0088] As described above, according to this embodiment, when the matching inspection is enabled, the front and back images are displayed side by side on the settings screen, and at the same time, the matching inspection area is automatically generated and displayed on the back side, thereby significantly reducing the burden of setting the matching inspection area.

[0089] <Embodiment 2> Embodiment 1 describes a method in which a matching inspection area is automatically generated for an area selected by the operator, and the operator makes final setting changes to the automatically generated area. However, because the generated matching inspection area has the same settings as the data inspection area, the position of the matching inspection area may be shifted, or the character orientation settings may be different. Specifically, even if the areas to be checked for matching within a page are the same on the front and back, the position of the inspection area may differ depending on the imposition during printing or the binding direction during double-sided printing. Alternatively, due to the composition of the content within the page, it may not be possible to place them in the same position, but they may be arranged with a certain degree of regularity considering design and visibility.

[0090] In this embodiment, we will describe a method to improve the accuracy of setting the automatically generated matching inspection area, taking into account the above-mentioned regularity, and to reduce the amount of manual setting required by the operator.

[0091] The following describes the differences between Embodiment 2 and Embodiment 1 described above. Parts not described in detail are the same as in Embodiment 1.

[0092] <Flowchart for generating matching test areas> The inspection setting flow in step S403 in this embodiment is as shown in the flowchart of Figure 7, but the flow for generating the matching inspection area in step S705, which is a feature of this embodiment, will be explained using the flowchart of Figure 9. This flowchart is realized when the CPU 302 of the inspection device 110 expands the program code stored in the ROM 304 into the RAM 303, and then reads and executes the program code expanded in the RAM 303.

[0093] In step S901, the CPU 302 receives the print settings for the print job executed for reference image registration from the RAM 303. The print settings are sent from the client PC 130 or print server 140 where the reference image registration print job was executed to the image forming apparatus 100 via the network 150. They are then sent to the inspection apparatus 110 via the communication I / F unit 301 and stored in the RAM 303. Specifically, the print settings refer to the image orientation (portrait / landscape), imposition, and binding settings for double-sided printing.

[0094] In step S902, the CPU 302 generates a candidate area for matching based on the print settings. Several examples of the generation of the candidate area for matching are explained using Figure 10. Here, the target of the matching check is a QR code, and it is assumed that its position on the page is the same. Images 1000 and 1001 in Figure 10(a) show the front and back images in the case of portrait orientation, 1 page layout, and short-edge binding. If the print settings received in step S901 are as described above, the candidate area for matching for data check area 1002 will be 1003. The setting for the candidate area for matching 1003 is point-symmetric with respect to data check area 1002, and because the top and bottom of the page are reversed, the orientation setting is rotated by 180 degrees.

[0095] Images 1004 and 1005 in Figure 10(b) show the front and back images in a case where the image orientation is portrait, the imposition is 2 pages, and the binding is on the short edge. If the print settings received in step S901 are as described above, the matching candidate area for the data inspection area 1006 will be 1007. The back side of the left page of image 1004 is the right page of image 1005. Therefore, the setting of the matching candidate area 1007 is to the right of the data inspection area 1006 by a distance of half the length of the long side of the print paper.

[0096] As described above, assuming that the areas to be checked for matching are in the same position on the plane, the system generates candidate areas for matching by determining the predicted position and orientation according to the print settings. Next, the CPU 302 checks the likelihood of matching the candidate areas.

[0097] In step S903, the CPU 302 analyzes the data inspection area and saves the analysis results to the RAM 303. The analysis here can be any method that extracts features within the area and confirms the degree of agreement between areas, such as OCR, barcode analysis, or pixel value histogram analysis.

[0098] In step S904, the CPU 302 analyzes the candidate regions for matching and saves the analysis results to the RAM 303.

[0099] In step S905, the CPU 302 reads the analysis results from step S903 and step S904 from RAM 303 and compares them. If the results are OCR results or barcode analysis results, it compares whether the content matches to determine if they match. If the features extracted based on pixel values ​​such as histograms, even if they do not match perfectly (100%), a threshold for the degree of matching (for example, 90%) is set, and if the match is above the threshold, it is determined to be a match. If the analysis results match (YES in step S905), the CPU 302 terminates the process of generating the matching inspection area. If the analysis results do not match, the CPU 302 saves the coordinates of the candidate matching inspection area and the result of the mismatch in RAM 303, and repeats the process from step S904 onwards for other predetermined candidate coordinate patterns.

[0100] The candidate coordinate patterns are explained using Figure 10(c). The candidate patterns determine the coordinate positions assuming that the data is arranged in a regular pattern. The inspection area 1008 is set in step S902 and is the position where the analysis results were determined not to match in step S905, and its center coordinates are (x,y). The coordinates of the top left of the image are (0,0) and the coordinates of the bottom right are (X,Y). The center coordinates of the first candidate pattern 1009 are (Xx,y), the center coordinates of the second candidate pattern 1010 are (Xx,Yy), and the center coordinates of the third candidate pattern 1011 are (x,Yy).

[0101] In step S906, the CPU 302 reads the results from RAM 303 to determine whether all candidate patterns 1009, 1010, and 1011 are mismatches. If the results for all candidate patterns are mismatches (YES in step S906), the CPU 302 terminates the matching test area generation process. At this time, the CPU 302 sets the matching test candidate area initially generated in step S902 as the matching test area and terminates the process. If there are still candidate patterns that have not been determined to be mismatches (NO in step S906), the CPU 302 changes the position of the matching test candidate area in step S907.

[0102] In step S908, the CPU 302 determines whether there are any overlap errors with other inspection areas in the newly set matching inspection candidate area. Specifically, if the print image inspection area and the data inspection area overlap, the CPU 302 detects the overlap and displays a warning (not shown) on the inspection setting screen 600. If no warning is displayed (NO in step S908), the CPU 302 returns to step S904 and processes. If a warning is displayed (YES in step S908), the CPU 302 saves the coordinates of the candidate pattern and the result of the mismatch to the RAM 303 and returns to step S906 and processes. The above describes the flow of generating matching inspection areas in Embodiment 2.

[0103] According to this embodiment, by setting the matching inspection area while considering the print settings, it is possible to set it with greater accuracy than in Embodiment 1. Furthermore, by determining candidate coordinates and performing analysis while considering the regularity of the design, the likelihood of correctly setting the matching inspection area increases. As a result, it is possible to reduce the operator's workload when setting the matching inspection area.

[0104] <Embodiment 3> Embodiment 2 describes a method for generating a matching inspection area while considering print settings and layout. In addition, by performing analysis when generating the matching inspection area, it is possible to improve the accuracy of the settings. However, the method of Embodiment 2 can only check a limited area within the image.

[0105] This embodiment describes a method to improve the accuracy of setting the matching inspection area and reduce manual settings by the operator by using image search to more flexibly search and set the matching inspection area from the entire image.

[0106] The following describes the differences between Embodiment 3 and Embodiments 1 and 2 described above. Parts not described in detail are the same as those in Embodiments 1 and 2.

[0107] <Flowchart for generating matching test areas> The inspection setting flow in step S403 in this embodiment is as shown in the flowchart of Figure 7, but the flow for generating the matching inspection area in step S705, which is a feature of this embodiment, will be explained using the flowchart of Figure 11. This flowchart is realized when the CPU 302 of the inspection device 110 expands the program code stored in the ROM 304 into the RAM 303, and then reads and executes the program code expanded in the RAM 303.

[0108] In step S1101, the CPU 302 performs a resolution conversion to reduce the resolution of the data inspection area and the image on the back side, and saves the converted image to the RAM 303. The resolution is reduced to lessen the load on the image search process and speed up the process. For example, if the resolution of the reference image registered is 300 dpi, the resolution conversion is performed to 100 dpi using the bicubic method. However, the method of resolution conversion is not limited to this, and any common method that does not significantly impair the characteristics of the image is acceptable. Note that the bicubic method is a common method, so a detailed explanation will be omitted.

[0109] Next, in step S1102, the CPU 302 reads the low-resolution image stored in RAM 303 and performs an image search. For example, the image search uses the SSIM (Structure Similarity) method to search for areas with high similarity to the data inspection area in the back-side image. However, the image search method is not limited to this, and other methods such as the PSNR (Peak Signal to Noise Ratio) method may also be used. Note that SSIM is a common method, so a detailed explanation will be omitted. The specific method of image search is to calculate the SSIM evaluation value while scanning the search area from the edge of the back-side image, and sequentially save it in a non-illustrated evaluation value list generated in RAM 303. The evaluation value list stores the coordinates of the search area in the low-resolution image and the evaluation value associated with it. When saving an evaluation value to the evaluation value list, the calculated value is compared with the value in the evaluation value list, and only if the calculated value is larger is the value in the evaluation value list overwritten. When the entire image has been searched, the evaluation value list is saved so that at least one data point remains, in descending order of evaluation value.

[0110] In step S1103, the CPU 302 analyzes the data inspection area of ​​the original image registered as a reference image. In step S1104, the CPU 302 calculates the coordinates of the 300dpi image registered as a reference image from the coordinates in the evaluation value list and analyzes the candidate matching inspection area of ​​the original image registered as a reference image. Here, the coordinates read from the evaluation value list are those with the highest evaluation value.

[0111] The analysis and the determination in step S1105 are the same as steps S903 to S905 of Embodiment 2, so a detailed explanation is omitted. If the analysis result is determined to be a match (YES in step S1105), the CPU 302 terminates the matching inspection area generation process and deletes the evaluation value list from RAM 303. If the analysis result is not determined to be a match (NO in step S1105), in step S1106, the CPU 302 determines whether all candidates stored in the evaluation value list have been analyzed. If all candidates have been analyzed (YES in step S1106), the CPU 302 terminates the matching inspection area generation process and deletes the evaluation value list from RAM 303. At this time, the CPU 302 sets the matching inspection area at the same coordinates as the data inspection area and terminates the process. If there are still unanalyzed candidates remaining (NO in step S1106), the process from steps S1103 to S1105 is repeated for the coordinate with the next highest evaluation value in the evaluation value list. If the analysis results for all candidates do not match, the process may be returned to step S1101 and the same process may be performed at a higher resolution (e.g., 200 dpi). The above describes the flow for generating the matching inspection area in Embodiment 3.

[0112] According to this embodiment, by using image search to search for and set the matching inspection area from the entire image, the likelihood of correctly setting the matching inspection area is increased. This makes it possible to reduce the operator's workload when setting the matching inspection area.

[0113] <Embodiment 4> Embodiment 3 described a method for generating matching inspection areas using image search. However, since image search and analysis take time, this may cause waiting times for the operator. There is a concern that the increased time required for setup may actually increase the setup burden on the operator.

[0114] In this embodiment, we describe a method to reduce the operator's workload when setting up the matching inspection area by having the operator specify the setting method at the beginning of setting up the matching inspection area, thereby enabling the matching inspection area to be set up more reliably and in a shorter time.

[0115] The following describes the differences between Embodiment 4 and Embodiments 1 to 3 described above. Parts not described in detail are the same as in Embodiment 1.

[0116] <Flowchart for generating matching test areas> The inspection setting flow in step S403 in this embodiment is as shown in the flowchart of Figure 7, but the flow for generating the matching inspection area in step S705, which is a feature of this embodiment, will be explained using Figure 12.

[0117] Screen 1200 is a selection screen for setting the matching inspection area. Screen 1200 shows five different setting methods, from 1201 to 1205. Image 1206, which has the letter "A" written on it, is the front image, and image 1207, which has the letter "B" written on it, is the back image. In both cases, the QR code is surrounded by a dotted line frame indicating that it is the inspection area.

[0118] 1201 indicates that the position and orientation of the matching inspection areas on the front and back surfaces are the same. 1202 indicates that the positions of the matching inspection areas on the front and back surfaces are symmetrical, and the orientation is the same.

[0119] 1203 indicates that the positions of the matching inspection areas on the front and back surfaces are point-symmetric, and the orientation is rotated 180 degrees. 1204 indicates that the positions of the matching inspection areas on the front and back surfaces are manually set by the operator, and the orientation is the same.

[0120] 1205 indicates that the positions of the matching inspection areas on the front and back surfaces are manually set by the operator, and the orientation is set by rotating 180 degrees.

[0121] When generating the matching inspection area in step S705, the CPU 302 first displays the selection screen 1200 on the inspection setting screen 600. The display method may be either by displaying it as an image in area 605 or by displaying it as radio buttons in setting area 641. After the operator selects one of the setting methods 1201 to 1205, the CPU 302 generates and displays the matching inspection area according to the selected setting method. For example, when setting method 1202 is selected, the CPU 302 displays Figure 8(c) in area 605. Alternatively, when setting method 1204 is selected, the CPU 302 displays Figure 8(b) in area 605. The processing from step S706 onward is the same as in Embodiment 1.

[0122] The above describes the flow of generating the matching inspection area in Embodiment 4.

[0123] According to this embodiment, by having the operator specify the method for setting the matching inspection area, it becomes possible to set the matching inspection area more reliably and in a shorter time, thereby reducing the burden on the operator when setting the matching inspection area.

[0124] <Embodiment 5> Embodiments 1 to 4 described a method for performing a matching check between the front and back surfaces. In these embodiments, the matching check area was one location on the front surface and one location on the back surface. However, in reality, matching checks may occur at multiple locations on either the front or back surface, or at three or more locations, such as one location on the front and two on the back surface.

[0125] In this embodiment, we will describe a method that is not limited to the front and back sides, and that also supports cases where there are three or more matching inspection areas.

[0126] The following describes the differences between Embodiment 5 and Embodiments 1 to 4 described above. Parts not described in detail are the same as in Embodiment 1.

[0127] <Flowchart for generating matching test areas> The inspection setting flow in step S403 in this embodiment is shown in the flowchart of Figure 7, but the flow for generating the matching inspection area in step S705, which is a feature of this embodiment, will be explained using Figure 13.

[0128] In Figure 13(a), 1300 is the selection screen for selecting the type of matching test, and in Figure 13(b), 1306 is the detailed settings screen for configuring the details of the matching test.

[0129] The front / back inspection button 1301 is a selection button for matching inspection, which sets one matching inspection area on the front and one on the back. The front / back inspection (multiple) button 1302 is a selection button for setting one matching inspection area on the front, one on the back, and one or more additional matching inspection areas on either the front or / or back.

[0130] The in-plane inspection button 1303 is a selection button for matching inspection, which sets two or more matching inspection areas within either the front or back surface.

[0131] When generating the matching inspection area in step S705, the CPU 302 first displays the selection screen 1300 on the inspection setting screen 600. The display method can be either by displaying it as an image in area 605 or by displaying it as radio buttons in setting area 641.

[0132] If the front / back inspection button 1301 is selected, the CPU 302 generates one matching inspection area on the back side and proceeds to step S706. In this case, any of the methods described above for generating the matching inspection area is acceptable.

[0133] If the "Inspect Front / Back (Multiple)" button 1302 is selected, the CPU 302 displays the detailed settings screen 1306 on the inspection settings screen 600.

[0134] Area 1307 is a window that displays the number of matching inspection areas to be set on the front surface, and its initial value is "1". Area 1308 is a window that displays the number of matching inspection areas to be set on the back surface, and its initial value is "1".

[0135] The triangular button 1309 is used to increase the number in area 1307. Each time it is pressed, the CPU 302 increments the number in area 1307 by 1 and redisplays it. The triangular button 1310 is used to decrease the number in area 1307. Each time it is pressed, the CPU 302 decrements the number in area 1307 by 1 and redisplays it.

[0136] Triangle button 1311 is a button for increasing the number in area 1308. Each time it is pressed, the CPU 302 increments the number in area 1308 by 1 and redisplays it. Triangle button 1312 is a button for decreasing the number in area 1308. Each time it is pressed, the CPU 302 decrements the number in area 1308 by 1 and redisplays it.

[0137] The OK button 1313 is used to save the settings from the detailed settings screen 1306 to the RAM 303 and to transition to the inspection settings screen 600. After the OK button 1313 is pressed, the CPU 302 generates inspection areas corresponding to the number of matching inspection areas on both the front and back sides saved in the RAM 303 and displays them in area 605. In this case, the settings for all matching inspection areas can be the same, but displaying them so that their positions do not overlap makes it easier for the operator to recognize multiple matching inspection areas.

[0138] If the in-plane inspection button 1303 is selected, the CPU 302 displays the detailed settings screen 1306 on the inspection settings screen 600. In this case, if the surface displayed in area 605 is the front surface, area 1308 and the triangle buttons 1311 and 1312 used for back surface settings are not needed and are grayed out. If the surface displayed in area 605 is the back surface, area 1307 and the triangle buttons 1309 and 1310 used for front surface settings are not needed and are grayed out. The processing after the number of inspection areas for the front or back surface is set and the OK button 1313 is pressed is as described above.

[0139] The above describes the flow for generating the matching inspection area in Embodiment 5.

[0140] According to this embodiment, it becomes possible to set up matching inspections for various cases, and it becomes possible to reduce the burden on the operator when setting the matching inspection area.

[0141] (Other embodiments) Although various examples and embodiments of this embodiment have been described above, the spirit and scope of this embodiment are not limited to the specific descriptions within this specification.

[0142] This embodiment can also be implemented by supplying a program that implements one or more of the functions of the above-described embodiment to a system or device via a network or storage medium, and by having one or more processors in the computer of that system or device read and execute the program. It can also be implemented by a circuit (e.g., an ASIC) that implements one or more functions.

Claims

1. An inspection device, RAM as a storage means for storing reference images, The system has a CPU as a control means that performs inspection of the read image obtained from a printed document based on the aforementioned reference image and inspection settings. The control means is As part of the inspection settings, the operator sets the data inspection settings to be used in the matching inspection and the first region which will be the inspection area in the matching inspection for the reference image, and upon receiving an instruction for matching inspection from the operator, a second region having the same data inspection settings as the first region is automatically set for the reference image. An inspection device characterized in that, in the inspection, it extracts data from the read image from regions corresponding to the first region and the second region, and checks whether the data extracted from the first region matches the data extracted from the second region.

2. The storage means stores predetermined data, The control means checks whether the data extracted from the first region and the data extracted from the second region match the correct CSV data stored in the storage means. The inspection apparatus according to feature 1.

3. The aforementioned reference image has at least two surfaces, The inspection apparatus according to claim 1, characterized in that the first surface in which the first region is set and the second surface in which the second region is set are generated on the same page.

4. The aforementioned reference image has at least two surfaces, The first surface, in which the first region is set, and the second surface, in which the second region is set, are generated on different pages. The inspection apparatus according to feature 1.

5. It has a user interface that displays a screen, The control means accepts setting changes for the second area via the user interface. The inspection apparatus according to feature 1.

6. It has a user interface that displays a screen, The control means sets the first area which is operated by an operator via the user interface. The inspection apparatus according to feature 1.

7. It has a user interface that displays a screen, The inspection apparatus according to claim 3 or 4, characterized in that when the control means receives an instruction for matching inspection from an operator via the user interface, it displays the first surface and the second surface side by side on the user interface.

8. The control means is The inspection apparatus according to claim 7, characterized in that when the first region displayed on the user interface is selected and the instruction for the matching inspection is received, the second region is automatically generated.

9. It has a user interface that displays a screen, The inspection apparatus according to claim 1, characterized in that the control means displays a warning on the user interface when the data extracted from the first region and the data extracted from the second region do not match.

10. The inspection apparatus according to claim 1, characterized in that when the control means receives an instruction for the matching inspection, it determines a position to automatically set the second area based on pre-set imposition information or binding setting information.

11. The inspection apparatus according to claim 1, characterized in that when the control means receives an instruction for the matching inspection, it extracts a plurality of candidate coordinates on the back surface of the reference image and identifies a location similar to the first region by image search to determine the position for setting the second region.

12. It has a user interface that displays a screen, The inspection apparatus according to claim 1, characterized in that the control means determines the position for automatically setting the second area when it receives an instruction for the matching inspection, by referring to the front-to-back alignment method selected by the operator via the user interface.

13. It has a user interface that displays a screen, The inspection apparatus according to claim 1, characterized in that the control means, after automatically setting the second area, allows an operator to perform position correction by dragging or numerical input via the user interface, and updates the final position of the second area based on the correction information.

Images