Inspection apparatus, and control method of inspection apparatus

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 apparatus and a control method for the inspection apparatus. [Background technology]

[0002] Conventionally, inspections (quality checks) to check whether printed matter is printed correctly have been performed manually, but in recent years, devices that perform inspections automatically have been used as post-processing for printing machines. Such inspection devices inspect variable areas (variable data) such as character strings and barcodes in variable printing. Examples include data readability inspections that check whether character strings and barcodes are readable, and data matching inspections that check the results of reading character strings and barcodes against the correct answer. In the following, data readability inspections and data matching inspections are referred to as data inspections. In addition, one type of data inspection is a match inspection.

[0003] Patent Document 1 proposes a front-back consistency inspection method for checking whether the results of reading data inspection areas set on the front and back sides match. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2022-69482 A Summary of the Invention [Problem to be solved by the invention]

[0005] However, in the method of Patent Document 1, when setting the inspection area for the coincidence inspection, the inspection area must be set on both the front and back sides, which poses a problem that the operator is burdened with setting the coincidence inspection. [Means for solving the problem]

[0006] The inspection device of the present invention is characterized by having a registration means for registering a received image as a reference image, an area setting means for setting a first area for a matching test in the reference image registered in the registration means, a generation means for generating a second area having the same settings as the first area set by the area setting means upon receiving an instruction for a matching test, an extraction means for extracting data from the first area and the second area in a read image read by a reading means from a printed matter on which an image has been formed by an image forming means, and an inspection means for inspecting whether the data extracted from the first area by the extraction means matches the data extracted from the second area by the extraction means. Effect of the Invention

[0007] According to the present invention, it is possible to significantly reduce the load imposed on the setting of the back side when setting the area for coincidence inspection. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram showing an example of a system configuration including an inspection apparatus according to an embodiment of the present invention. [Diagram 2] FIG. 1 is an example of an internal configuration diagram of an image forming apparatus 100 according to an embodiment of the present invention. [Diagram 3] 1 is an example of an internal configuration diagram of an inspection device 110 according to the present embodiment. [Figure 4] 1 is a flowchart showing an example of an entire inspection process according to the present embodiment. [Diagram 5] An example of a UI screen for job management in this embodiment. [Figure 6] An example of a UI screen for test settings in this embodiment [Figure 7] An example of a flowchart of the test setting (S403) in the first embodiment [Figure 8] An example of a match inspection area display in the first embodiment [Figure 9] 13 is a flowchart showing an example of a process for generating a matching check area (S705) according to the second embodiment. [Figure 10] An example of setting a coincidence inspection area in the second embodiment [Figure 11] 13 is a flowchart showing an example of a process for generating a match check area (S705) according to the third embodiment. [Figure 12] An example of a UI when generating a matching check area (S705) in the fourth embodiment [Figure 13] An example of a UI when generating a matching check area (S705) in the fifth embodiment DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[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 of the combinations of features described in each embodiment are necessarily essential to the solution of the present invention.

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

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

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

[0013] The inspection device 110 inspects whether there are defects in the printed matter conveyed in sequence from the image forming device 100. Here, a defect is something that reduces the quality of the printed matter, such as stains caused by color material adhering to unintended locations during printing, or color loss caused by insufficient color material adhering to intended locations.

[0014] Furthermore, the inspection device 110 inspects the variable area portion in variable printing including a variable area portion such as a one-dimensional code such as a character string or a barcode, or a two-dimensional code such as a QR code (registered trademark). For example, a data readability inspection is performed to check whether the character string or the barcode can be read, and a data matching inspection is performed to match the read result of the character string or the barcode with a correct answer. Furthermore, a front-back match inspection is performed to check whether the read results of the data inspection areas set on the front and back sides match. That is, the inspection device 110 performs a print image inspection to detect abnormalities in the picture portion of the printed matter, and a data inspection including a data readability inspection and a data matching inspection. Note that the inspection device 110 does not necessarily have to have an inspection processing unit that performs the print image inspection and the data inspection inside, and may be configured to perform the inspection processing by, for example, an information processing device (not shown) as an inspection PC connected to the inspection device 110 so as to be able to communicate with the inspection device 110. Note that in this embodiment, the barcode inspection refers to an inspection that can also inspect two-dimensional codes such as a QR code. Also, the inspection system in this embodiment is configured to at least inspect the printed matter by the inspection device 110.

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

[0016] Image forming apparatus 100 is connected to client PC 130 and print server 140 via network 150, and is further connected to inspection apparatus 110 and finisher 120 via communication cables. In addition to image forming apparatus 100, inspection apparatus 110 is also connected to finisher 120 via communication cables. This embodiment will be described using an in-line inspection machine that performs image formation, inspection, post-processing, and paper discharge in an integrated manner, as an example, but this is not intended to limit the present invention.

[0017] [Image forming device configuration] 2 is a diagram showing 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 a printout by printing the print data on a recording sheet (paper, sheet). The UI unit 220 displays a screen and accepts instructions from an operator to the image forming apparatus 100, such as the selection of paper information. The image forming apparatus 100 is composed of the controller 200, the printer unit 210, and the UI unit 220 described above.

[0018] Reference numerals 201 to 208 are components of the controller 200. A network I / F (interface) unit 201 transmits and receives data to and from the client PC 130 and the print server 140 via the network 150. A CPU 202 controls the image forming apparatus 100 as a whole.

[0019] The RAM 203 is a work area when the CPU 202 executes various commands, and the ROM 204 stores program data executed by the CPU 202 at startup, setting data for the controller 200, etc. The image processing unit 205 performs RIP (Raster Image Processor) processing to convert image and document data received from the network 150 into print data.

[0020] In this embodiment, the RIP process does not have to be performed by the image processing unit 205, and may be performed by, for example, an information processing device (not shown) communicably connected to the image forming apparatus 100.

[0021] An engine I / F (interface) unit 206 transmits print data to a printer unit 210. A communication I / F unit 207 communicates with the inspection device 110 and the finisher 120. Reference numeral 208 denotes an internal bus (system bus).

[0022] Images and documents created on client PC 130 or print server 140 on network 150 are transmitted as PDL data to image forming apparatus 100 via a network (e.g., a local area network). Note that a print job for an image, document, etc. may be transmitted to an information processing device (not shown) via the network and managed by the information processing device. The print job may then be transmitted from the information processing device to image forming apparatus 100 via network 150, and image forming apparatus 100 may perform processing to print on paper.

[0023] The transmitted PDL data is stored in the RAM 203 via the network I / F unit 201. A print instruction from an operator of the UI unit 220 is also stored in the RAM 203 via the internal bus 208. A print instruction from the operator is, for example, a selection of a 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. The image processing to convert it into print data means, for example, rasterizing the PDL data, converting it into multi-value bitmap data, and converting it into binary bitmap data by performing screen processing or the like. 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 on a recording sheet using color materials. The CPU 202 issues instructions to the printer unit 210 based on the print instructions from the operator stored in the RAM 203. For example, when the operator instructs to print on coated paper, the CPU 202 issues an instruction to the printer unit 210 to output paper from a paper cassette (not shown) in the image forming apparatus 100 in which coated paper is stored. The various processes from receiving the above-mentioned PDL data to printing on paper are controlled by the CPU 202, and a full-color toner image is formed on the paper.

[0026] [Internal configuration of inspection device 110] 3 is a diagram showing the internal configuration of the inspection device 110. An inspection control unit 300 controls the entire inspection device 110 and controls the inspection process for checking whether or not there are defects in printed matter.

[0027] The image reading unit 310 reads the printed material conveyed 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 UI unit for the operator to set the inspection device 110 and display the inspection results to the operator. The setting of the inspection device 110 performed by the operator here refers to the items of defects to be inspected when inspecting a printed matter. The inspection items are, for example, round defects (spots) and linear defects (streaks). The inspection device 110 is composed of the above-mentioned inspection control unit 300, image reading unit 310, and UI unit 320. In this embodiment, the UI unit 320 is composed of a display unit that displays a screen and a display control unit that controls the screen displayed on the display unit. The setting of the inspection device 110 and the display of the inspection results performed by the UI unit 320 may be displayed and instructions may be received by an external device such as the UI unit 220 of the image forming device 100 described above, an inspection PC (not shown), or an information processing device (not shown).

[0029] Reference numerals 301 to 306 are components of the inspection control unit 300. The communication I / F (interface) unit 301 transmits and receives data to and from the image forming apparatus 100, the finisher 120, and the inserter 160. The CPU 302 controls the entire inspection device 110. The RAM 303 is a work area when the CPU 302 executes various commands, and the ROM 304 stores program data executed by the CPU 302 at startup, setting data for the inspection control unit 300, and the like. A correct answer CSV file, which will be described later, is also stored in the ROM 304. The inspection processing unit 305 inspects whether or not there is a defect in the printed matter. The internal bus 306 is a system bus.

[0030] (Print image inspection) An overview of the print image inspection performed by the inspection device 110 will be described. The inspection device 110 uses the image reading unit 310 to read the printed material conveyed from the image forming device 100 and acquires a scanned image (scanned image) of the inspection target. The acquired scanned image of the inspection target is stored in RAM 303. Next, the inspection device 110 uses the inspection processing unit 305 to acquire a difference value between a reference image previously stored in RAM 303 as a correct image and the scanned image of the inspection target.

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

[0032] (Data Inspection) The data inspection performed by the inspection device 110 will be outlined below. The inspection device 110 reads the printed matter conveyed from the image forming device 100 in sequence by the image reading unit 310, and acquires a scanned image of the inspection target. The acquired scanned image of the inspection target is 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 the character string, barcode, or QR code in the scanned image. This is performed using a character font for character recognition (OCR) that is set in advance, and a barcode standard, and OCR processing is performed on the character. Decoding processing is performed on the barcode. In the data inspection, an inspection is performed to check whether the character string or barcode in the area set for data inspection can be read. If it can be read, an OK judgment is made, and if it cannot be read, an NG judgment is made. It is also possible to perform a data comparison inspection to check whether the extracted data, that is, the read character string or barcode result, matches the corresponding data (correct data) of a correct CSV file prepared in advance. Here too, if the data matches as a result of the comparison, an OK judgment is made, and if it does not match, an NG judgment is made. The results of the inspection are stored in RAM 303, such as the results of character strings and barcodes read from printed matter, the results of matching with correct data, and position information of the characters and barcodes read when displayed on the UI section 320.

[0033] (Front and back consistency inspection) An overview of the front and back match inspection performed by the inspection device 110 will be described. As with data inspection, the inspection device 110 reads the printed material and performs extraction processing to extract data from character strings and barcodes / QR codes in the read scanned image. In the front and back match inspection, it is determined whether the data extracted from the front and the data extracted from the back match. If they match, an OK decision is made, and if they do not match, an NG decision is made. The results of the inspection are stored in the RAM 303, and for example, the results of the character strings and barcodes read from the printed material, the results of whether the front and back match, position information of the characters and barcodes read when displayed on the UI unit 320, etc. are stored.

[0034] After completing the above-mentioned print image inspection, data inspection, and front / back consistency inspection, the inspection device 110 instructs the UI unit 320 to display the inspection results stored in the RAM 303 via the CPU 302. The inspection results are displayed on the UI unit 320 so that the operator can recognize the inspection results. Furthermore, if a defective printed matter occurs or a certain number of defective printed matter occurs consecutively, the inspection device 110 causes the CPU 302 to transmit the above information to the image forming device 100 via the communication I / F unit 301.

[0035] The information that a defective printed matter has occurred is received by controller 200 via communication I / F unit 207. When controller 200 receives the above information, CPU 202 instructs printer unit 210 to stop printing. Image forming apparatus 100 stops the printing operation when printer unit 210 is instructed to stop printing.

[0036] Furthermore, the inspection device 110 also transmits information to the finisher 120 via the communication I / F unit 301 based on the inspection results stored in the RAM 303 by the CPU 302. The information transmitted to the finisher 120 is information on whether or not there is a defect in the printed matter. Using the received information, the finisher 120 discharges printed matter without defects to a normal paper discharge tray, and discharges printed matter with defects to a tray other than the normal paper discharge tray.

[0037] <Overall inspection flow> Next, the overall flow from the registration work before starting the inspection in the inspection device 110 to the execution of the inspection will be described with reference to the flowchart in Fig. 4. This flowchart is realized by the CPU 302 expanding the program code stored in the ROM 304 into the RAM 303, and reading and executing the program code expanded into the RAM.

[0038] In step S401, the CPU 302 registers a character font. The character font registered here is used during data inspection. A character font is data that associates character images and character codes of characters required for character recognition (OCR) performed during data inspection. The procedure for creating a character font is as follows: first, the inspection device 110 waits in a character font image reading mode and receives a print job for creating a character font from the client PC 130. The inspection device 110 receives the character font job from the client PC 130 and reads the character font image. When printing is performed, the inspection device 110 detects the conveyance of a printed matter from the image forming device 100, scans the printed matter with the image reading unit 310, and stores the scanned image in the RAM 303 of the inspection device 110. A character to be OCR is extracted one by one from the scanned image, and an operator inputs a character code for the extracted character image, thereby creating a character font. The created character font is stored in the RAM 303 of the inspection device 110. Although the method for creating a character font in this embodiment has been described here, any method may be used as long as it can create data in which a character code is associated with each character image extracted from a scanned image. Note that there may be cases where data inspection is not performed and only print image inspection is performed. In this case, S401 is not performed and the process proceeds to S402.

[0039] In step S402, the CPU 302 registers a reference image that is to be a correct image for the inspection. The inspection device 110 waits in a reference image reading mode, and executes a print job for registering the reference image from the client PC 130. When printing is executed, the inspection device 110 detects the conveyance of the printed matter, scans the printed matter with the image reading unit 310, and the scanned image is stored as a 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 limited to this. For example, a method of registering an image RIP-processed by the print server 140 or the image processing unit 205 of the image forming device 100 as a reference image may be used.

[0040] In step S403, the CPU 302 accepts the inspection settings and stores various inspection setting values ​​such as the inspection area and the 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, CPU 302 receives an inspection print job from client PC 130, detects the transport of paper, scans the paper with image reading unit 310, and stores the scanned image in RAM 303 of inspection device 110. Then, pattern inspection is performed using the image obtained by scanning the inspection job and the reference image registered in S402, using the inspection setting values ​​set in S403. Also, data inspection is performed using the character font registered in step S401 and the inspection settings set in step S403. The processing of this flowchart ends.

[0042] FIG. 5 shows an example of a 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 up, or when an application is started up from the UI unit 320 by an operator's operation.

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

[0045] A button 501 is a button for erasing the display on the screen 500. A button 502 is a button for creating a new inspection job and for registering a reference image.

[0046] Button 503 is a button for duplicating an inspection job that has already been created. An inspection job selected in the inspection job list 508 is duplicated. By making a duplicate, it is possible to duplicate the reference image and inspection settings and perform a new inspection. Pressing button 503 transitions to the inspection setting screen shown in FIG. 6.

[0047] Button 504 is a delete button, which deletes the inspection job selected in inspection job list 508. It is also possible to delete multiple inspection jobs simultaneously by selecting multiple inspection jobs and pressing button 504. Button 505 is an inspection setting button, which performs inspection settings for an inspection job for which reference image registration has been completed.

[0048] A button 506 is an inspection button for inspecting an inspection job for which reference image registration and inspection settings have been completed. A button 507 is a font registration button for registering character fonts.

[0049] [Inspection Settings] Next, the examination settings will be described with reference to Fig. 6. Fig. 6(a) shows an example of an examination setting screen 600 displayed on the UI unit 320 of the examination device 110 for performing examination settings.

[0050] A button 601 is a reference image change button, which is used when changing the reference image. A button 602 is an inspection area selection button, which is pressed by the operator when he / she wishes to select an area that has already been set.

[0051] A button 603 is an inspection area delete button, which is pressed by the operator when the selected area is to be deleted. A button 604 is a button for rotating the image displayed in an area 605 .

[0052] Area 605 is a display area that displays the loaded reference image. When multiple sheets are loaded, the image to be displayed is switched with button 610. The front and back sides of the loaded sheets are also switched with button 610. Specifically, each time right arrow button 610 is pressed, the pages are switched in the order of the front side of the first sheet, the back side of the first sheet, the front side of the second sheet, and the back side of the second sheet.

[0053] A button 611 is an OK button for saving the settings of the screen 600 and transitioning to a job management screen 500 shown in Fig. 5. Pressing the button 611 may also transition to an inspection screen (not shown) so that an inspection can be performed. A button 612 is a cancel button for transitioning to the job management screen 500 shown in Fig. 5 without saving the settings of the screen 600.

[0054] A 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 the print image inspection area.

[0055] Button 622 is a button that is pressed by the operator when creating a new character inspection or barcode inspection area. After pressing the button, the operator sets the inspection area on the reference image displayed in area 605. Character area 607 shows an example of a set character inspection area. Area 608 shows an example of a set barcode inspection area. Note that in FIG. 6, areas 606, character area 607, and area 608 are drawn with the same black dotted line, but they may be displayed so that they are distinguishable as areas where different processes are performed. For example, the frames of areas where different processes are performed may be displayed in different colors or with dashed lines. Also, the operator may be able to select the display color of these frames.

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

[0057] Setting item 631 is a setting for misalignment inspection, and sets the allowable amount of misalignment of the print position from the reference image. In this embodiment, an example is shown in which the amount of misalignment is specified by the operator when detecting a misalignment of 2 mm or more. In other words, the value specified by the operator here corresponds to the threshold value for misalignment detection. If a misalignment equal to or greater than the threshold value set here is detected, the inspection is determined to be NG.

[0058] The setting area 632 is a UI group for making settings for the area currently selected in area 605. The setting items 633 set the scope of the selected area. If nothing is selected, the selected inspection area will be placed only 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 page on the same side depending on whether the selected inspection area is placed on the front or back side 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 a detection level for a round defect (dot) or a linear defect (streak). The detection level is a parameter that is set in stages for determining the size of a detected defect for each feature of the defect. For example, there are five stages, 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 shows that the operator has selected level 4 for the inspection level setting for defects (dots) and level 4 for the inspection level setting for defects (streaks).

[0060] 6(b) is an example of an inspection setting screen when the currently selected setting area is a data area. The setting area 641 is a group of UIs for making settings for the data inspection area that is displayed when a data inspection area is selected in the area 605.

[0061] In this example, the currently selected area is assumed to be character area 607, but similar settings are also made for character area 609. Note that area 605 displays selected areas so that they can be distinguished from unselected areas.

[0062] The settings area 642 sets the scope of the selected area. If nothing is selected, the selected inspection area will be placed only 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 page depending on whether the selected inspection area is located on the front or back side of the sheet. If "All Pages" is selected, the selected inspection area will be placed on all pages.

[0063] The setting area 643 is an area for setting the correct CSV file to be compared when performing a matching test. A file is selected by pressing button 644, and the selected file name is displayed. The specification of the correct CSV file is common to both character and barcode tests. The setting area 645 is used to set the currently selected data inspection area. Here, the orientation, selection of the character area or barcode inspection area, font type, barcode type, whether or not to perform a matching test, and specification of the columns of the correct CSV file for the matching test are specified. These settings required for data inspection are called inspection parameters.

[0064] Setting item 646 sets the character orientation in character area 607. Setting items 647 and 648 specify whether the selected area is to be inspected for a character string or a barcode. Setting item 649 sets the font used for OCR processing of character area 607. Setting item 650 sets the type of barcode when barcode inspection is selected in setting item 648.

[0065] Whether or not to perform a comparison check is set in setting item 651. If a comparison check is set to "Yes," OCR processing is performed on the character area 607 using the correct answer CSV file specified in setting area 643 and the column number specified in setting item 652, and a comparison check is performed between the read character string and the character string specified in the correct answer CSV.

[0066] In the setting item 653, whether or not to perform a coincidence check is set. A coincidence check is a check to see if the read results of two or more check areas match. For example, a coincidence check area (not shown) for performing a coincidence check is set on the opposite side of the currently selected character area 607, and it is checked whether the read results of the areas match on the front and back sides. In particular, a check to see if an object on the front side matches an object on the back side may be called a front and back check or a front and back match check.

[0067] Here, examples of data inspections are a data readability inspection to check whether a character string or a barcode can be read, a data comparison inspection to check the results of reading a character string or a barcode against the correct answer, and a front / back match inspection to check whether the results of reading the front and back match. However, the data inspection is not limited to these. For example, it may be a serial number inspection to check whether the read results are serial numbers, or a match inspection to check whether the results of reading multiple points on a surface match, as long as it reads a character string or a barcode and performs the inspection.

[0068] <Test setting flow> Next, the flow of the inspection setting in S403 will be described with reference to the flowchart in Fig. 7. This flowchart is realized by the CPU 302 of the inspection device 110 expanding the program code stored in the ROM 304 into the RAM 303, and reading and executing the program code expanded into the RAM 303.

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

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

[0071] In step S703, the CPU 302 determines whether or not a match check is set in the check setting in step S702. If a match check is set (YES in step S703), the process proceeds to step S704. If a match check is not set (NO in step S703), the process proceeds to step S707.

[0072] In step S704, CPU 302 determines whether a match check area has already been created. The match check area refers to an area where a match check is performed with the data check area set in step S702. If a data check area has been newly created, the match check area has not yet been created (YES in step S703), so the process proceeds to step S705. If the setting of the data check area has been changed, the match 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 as those set for the selected inspection area, such as the orientation and character type. The matching inspection area generated here may be generated within the same page as the sheet on which the data inspection area was set in S702, or may be generated on a different page. It may also be generated on a different page of the same sheet.

[0074] In step S706, the CPU 302 accepts a change to the setting of the inspection area by the operator. When changing the setting of the match inspection area, there may be restrictions on the items that can be changed, or confirmation may be required when making a change, but this will be described in detail later.

[0075] The generation of the matching inspection area will be specifically described with reference to FIG. 8. FIG. 8(a) shows the area 605 when the data inspection area is set in step S702. An image 801 is a reference image, and a QR code in the image is set as the data inspection area 802. "Setting" means that all the required items are set for the setting area 641 in FIG. 6(b). Required items are, for example, the orientation, the selection of the character area or the barcode inspection area, the font type, and the barcode type for the data readability inspection. For the data verification inspection, the orientation, the selection of the character area or the barcode inspection area, the font type, the barcode type, the presence or absence of the verification inspection, and the column of the correct CSV file at the time of the verification inspection. When the matching inspection is enabled for the data inspection area 802, it is desirable to do so after the required items for the setting described above 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 load on the operator. Therefore, the setting items 653 for the matching inspection are grayed out until the required items are set for the data inspection area 802. Alternatively, when the matching check setting item 653 is enabled in a state where the required items have not been set, a warning may be issued.

[0076] FIG. 8(b) shows area 605 when the matching check area is set in step S705. Image 803, which is displayed alongside image 801, is an image of the back side of image 801, and has the same QR code as image 801. When data check area 802 is selected and a matching check is set, CPU 302 generates and displays matching check area 804. At this time, the selected area moves from data check area 802 to matching check area 804. The settings of matching check area 804 are all the same as data check area 802, except that it is placed on the back side of data check area 802. Therefore, at the time of generating matching check area 804, the position of matching check area 804 does not match the position of the QR code in image 803. Here, the operator changes the settings of matching check area 804.

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

[0078] FIG. 8(c) shows the matching check area 805 after the setting change is completed. The setting change here is a change in the position of the matching check area 804. The method of changing the position may be any method that allows the operator to appropriately change the setting of the check area, such as by dragging and dropping the matching check area 804 or by the operator reselecting the location of the QR code. The operator may also change other setting items related to the data check as necessary. However, when a data matching check is set for the data check area 802, it is possible to not accept setting changes to the correct answer CSV file in the setting area 643, whether or not to perform a matching check in the setting area 651, and the column number in the setting area 652. As a method for prohibiting the setting change, any method that can notify that the setting cannot be changed may be used, such as by graying out items for which the setting change is not accepted, or by issuing a warning when the setting is changed.

[0079] Even when changing the inspection settings again after completing the setting of the matching inspection area once, the CPU 302 arranges the front and back images as shown in FIG. 8(c) to allow the inspection settings to be changed. When the setting of the data inspection area 802 is changed, whether or not to apply the setting change to the matching inspection area 805 can be determined in advance in the initial setting by displaying a pop-up on the UI each time the setting is changed. Also, in FIG. 8(b), the data inspection area 802 and the matching inspection areas 804 and 805 are drawn with the same black dashed lines. For example, the automatically generated matching inspection areas 804 and 805 may be displayed with different line color, shape, thickness, action, etc. from the data inspection area 802, and may be displayed the same as the data inspection area 802 after the setting is completed. Note that, if you want to perform a matching inspection for two locations, a character string and a QR code, as shown in FIG. 8(d), for example, you specify the data inspection area 802 and then specify a matching inspection to generate the data inspection area 805. Furthermore, by specifying a data inspection area 806, then specifying a match inspection, and generating a data inspection area 807, it is possible to specify match inspections in two locations on one sheet.

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

[0081] [Match Check] So far, the setting flow for the coincidence check has been explained. Next, the contents of the coincidence check and the display method will be explained.

[0082] As mentioned above, a match test is one type of data test, and is a test to check whether the data matches. Therefore, the display format of the data does not have to be the same, and it can be character strings or a character string and a barcode, as long as the final data read results match.

[0083] There are several possible methods for the match check. Here, if a match check is set for data A and data B in certain print data, data A and data B are checked using the check method described below. First, a case will be described where only checking whether the read results of the areas where the match check is set match will be explained. CPU 302 sequentially saves the read results of all areas where the match check is set in RAM 303, compares the saved read results, and judges whether the data matches or does not match. If there is even one mismatched data, the match check is NG.

[0084] Next, a case where all the matching check areas check the same CSV data as the correct answer will be described. The CPU 302 sequentially saves the results of the data matching check for all the areas set for matching check in the RAM 303 and judges whether there is any NG. If there is even one NG, the matching check is NG.

[0085] Furthermore, a case will be described in which a data matching test is performed only in one matching test area, and the other matching test areas are checked to see if their read results match those of the test areas where the data matching test was performed. The CPU 302 saves the results of the data matching test and the read results of all the matching test areas, compares the saved read results, and judges whether the data matches or does not match. If the data matching test is NG or there is even one mismatched data, the match test is NG.

[0086] An example of a method for displaying the match check area will be described with reference to Fig. 8(d). Fig. 8(d) shows an example in which a match check for data A and a match check for data B are set for the front and back of a printed matter.

[0087] Characters 806 and 807 are subject to a matching check separate from data A displayed in the QR code of the above-mentioned check areas 802 and 805. Also, icons 808 and 809 are icons added to the matching check areas. Adding the same icon to the matching check areas makes it easier to distinguish between the areas where a matching check is to be performed. 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 the matching check areas is not limited to this, and any method that makes it easy to recognize and distinguish between the areas where a matching check is to be performed, such as adding a mark or changing the pattern, thickness, or color of the enclosing line, may be used.

[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 setting screen, and at the same time, a matching inspection area is automatically generated and displayed on the back side, thereby significantly reducing the load associated with setting the matching inspection area.

[0089] <Embodiment 2> In the first embodiment, a method has been described in which a matching inspection area for an area selected by an operator is automatically generated, and the operator further performs final setting changes to the automatically generated area. However, since 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 direction may be set differently. Specifically, even if the area for performing the in-plane matching inspection is the same on the front and back, the position of the inspection area may differ depending on the imposition at the time of printing or the binding direction at the time of double-sided printing. Or, although it is not possible to place them in the same position due to the configuration of the content on the plane, they may be arranged with a certain degree of regularity in consideration of design and visibility.

[0090] In this embodiment, a method will be described in which the accuracy of setting the automatically generated coincidence check area is improved by taking the above-mentioned regularity into consideration, and manual setting by the operator is reduced.

[0091] Hereinafter, the second embodiment will be described with respect to the differences from the first embodiment. Note that the parts not described in detail are the same as the first embodiment.

[0092] <Flow of generating match check area> The inspection setting flow in step S403 in this embodiment is as shown in the flowchart in Fig. 7, but the matching inspection area generation flow in step S705, which is a feature of this embodiment, will be described using the flowchart in Fig. 9. This flowchart is realized by the CPU 302 of the inspection device 110 expanding the program code stored in the ROM 304 into the RAM 303, and reading and executing the program code expanded into the RAM 303.

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

[0094] In step S902, the CPU 302 generates a match check candidate area based on the print settings. Several examples of generating a match check candidate area will be described with reference to FIG. 10. Here, it is assumed that the target of the match check is a QR code, and that the position within the page is the same. Images 1000 and 1001 in FIG. 10(a) show front and back images in a case where the image orientation is portrait, the imposition is one page, and the document is bound on the short edge. If the print settings received in step S901 are as described above, the match check candidate area for the data check area 1002 will be 1003. The setting of the match check candidate area 1003 is a point-symmetrical position with respect to the data check area 1002, and since the page is upside down, the orientation setting is rotated 180 degrees.

[0095] 10B show front and back images in a case where the image orientation is portrait, the imposition is two pages, and the document is bound on the short edge. If the print settings received in step S901 are as described above, the match inspection candidate area for data inspection area 1006 is 1007. The back side of the left page of image 1004 is the right page of image 1005. Therefore, the setting of match inspection candidate area 1007 is a position shifted to the right of data inspection area 1006 by half the distance of the long side of the printing paper.

[0096] As described above, on the premise that the areas to be subjected to the matching test are at the same position within the plane, the CPU 302 generates the matching test candidate areas by determining the estimated positions and orientations according to the print settings. Next, the CPU 302 checks the accuracy of the matching test candidate areas.

[0097] In step S903, the CPU 302 analyzes the data inspection area and stores the analysis result in the RAM 303. The analysis here may be any analysis method, such as OCR, barcode analysis, or pixel value histogram analysis, that can extract features within the area and check the degree of match between areas.

[0098] In step S 904 , the CPU 302 analyzes the match check candidate regions and stores the analysis results in the RAM 303 .

[0099] In step S905, CPU 302 reads out from RAM 303 the analysis result in step S903 and the analysis result in step S904, and compares them. If the results are OCR results or barcode analysis results, the contents are compared to determine whether they match. If the features are extracted based on pixel values ​​such as histograms, a threshold value for the degree of match (e.g., 90%) is set, and it is determined that there is a match if the threshold value is exceeded, even if there is not a perfect match (100%). If the analysis results match (YES in step S905), CPU 302 ends the process of generating the match check area. If the analysis results do not match, CPU 302 saves the coordinates of the match check candidate area and the result of mismatch in RAM 303, and repeats the process from step S904 onwards for other candidate patterns of predetermined coordinates.

[0100] The candidate pattern of coordinates will be described with reference to FIG. 10(c). The candidate pattern is for determining the coordinate position on the assumption that data is arranged with regularity. The inspection area 1008 is set in step S902, and is assumed to be a position where the analysis result is determined not to match in step S905, and its center coordinates are (x, y). The coordinates of the upper left corner of the image are (0, 0), and the coordinates of the lower right corner 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 the RAM 303 and determines whether there was a mismatch for all of the candidate patterns 1009, 1010, and 1011. If the results for all of the candidate patterns are a mismatch (YES in step S906), the CPU 302 ends the process of generating the match check area. At this time, the CPU 302 sets the match check candidate area generated first in step S902 as the match check area and ends the process. If there is a candidate pattern that has not yet been determined to be a mismatch (NO in step S906), the CPU 302 changes the position of the match check candidate area in step S907.

[0102] In step S908, CPU 302 determines whether or not there is an overlap error with another inspection area for the newly set match inspection candidate area. Specifically, if the print image inspection area and the data inspection area overlap, CPU 302 determines the overlap and displays a warning (not shown) on the inspection setting screen 600. If no warning has been issued (NO in step S908), CPU 302 returns to step S904 and performs processing. If a warning has been issued (YES in step S908), CPU 302 stores the coordinates of the candidate pattern and the mismatch result in RAM 303, and returns to step S906 and performs processing. This concludes the description of the flow for generating a match inspection area in embodiment 2.

[0103] According to this embodiment, the matching inspection area is set in consideration of the print settings, making it possible to set the area more accurately than in embodiment 1. Also, by considering the regularity of the design and performing analysis to identify candidate coordinates, the likelihood of correctly setting the matching inspection area is increased. As a result, it is possible to reduce the burden on the operator in setting the matching inspection area.

[0104] <Embodiment 3> In the second embodiment, a method for generating a matching inspection area taking into consideration print settings and layout has been described. In addition, by performing analysis when generating the matching inspection area, it is possible to improve the accuracy at the time of setting. However, the method of the second embodiment can only check a limited area in an image.

[0105] In this embodiment, a method is described in which image search is used to more flexibly search for and set a matching inspection area from the entire image, thereby improving the accuracy of setting the matching inspection area and reducing the amount of manual setting by the operator.

[0106] Hereinafter, the third embodiment will be described with respect to the differences from the first and second embodiments. Note that the parts not described in detail are the same as the first and second embodiments.

[0107] <Flow of generating match check area> The inspection setting flow in step S403 in this embodiment is as shown in the flowchart in Fig. 7, but the matching inspection area generation flow in step S705, which is a feature of this embodiment, will be described using the flowchart in Fig. 11. This flowchart is realized by the CPU 302 of the inspection device 110 expanding the program code stored in the ROM 304 into the RAM 303, and reading and executing the program code expanded into the RAM 303.

[0108] In step S1101, CPU 302 performs resolution conversion to lower the resolution of the image in the data inspection area and the back side, and stores the converted image in RAM 303. The resolution is lowered in order to reduce the load on the image search process and speed up the process. For example, if the resolution of the image registered as the reference image is 300 dpi, resolution conversion is performed to 100 dpi using the bicubic method. However, the method of resolution conversion is not limited to this, and any general method may be used as long as it does not significantly impair the characteristics of the image. Note that since the bicubic method is a general method, a detailed explanation will be omitted.

[0109] Next, in step S1102, the CPU 302 reads out the low-resolution image stored in the RAM 303 and performs image search. For example, the image search uses the SSIM (Structure SIMilarity) method to search the image on the back side for an area that is highly similar to the data inspection area. However, the image search method is not limited to this, and other methods such as the PSNR (Peak Signal to Noise Ratio) method may be used. Note that the SSIM is also a common method, so a detailed description 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 image on the back side, and sequentially store the SSIM evaluation value in an evaluation value list (not shown) generated in the RAM 303. The evaluation value list stores the coordinates of the search area in the low-resolution image and the evaluation value in association with each other. When the evaluation value is stored in 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, the value in the evaluation value list is overwritten. When the entire image has been searched, the evaluation value list is stored in order of the highest evaluation value, so that at least one data remains.

[0110] In step S1103, the CPU 302 analyzes the data inspection area of ​​the original image registered as the reference image. In step S1104, the CPU 302 calculates the coordinates of the 300 dpi image registered as the reference image from the coordinates in the evaluation value list, and analyzes the matching inspection candidate area of ​​the original image registered as the 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 here are the same as those in steps S903 to S905 in the second embodiment, and therefore detailed description thereof will be omitted. If the analysis result is determined to be a match (YES in step S1105), the CPU 302 ends the process of generating the match check area, and deletes the evaluation value list from the RAM 303. If the analysis result is not determined to be a match (NO in step S1105), the CPU 302 determines in step S1106 whether all the candidates stored in the evaluation value list have been analyzed. If all the candidates have been analyzed (YES in step S1106), the CPU 302 ends the process of generating the match check area, and deletes the evaluation value list from the RAM 303. At this time, the CPU 302 sets the match check area at the same coordinates as the data check area, and ends the process. If there are candidates remaining that have not been analyzed (NO in step S1106), the process of steps S1103 to S1105 is repeated for the coordinates with the next highest evaluation value in the evaluation value list. If the analysis results of all the candidates do not match, the process may return to step S1101 and the same process may be performed at a higher resolution (for example, 200 dpi). This concludes the description of the flow of generating the match check area in the third embodiment.

[0112] According to the present embodiment, the possibility of correctly setting the matching inspection area is increased by searching and setting the matching inspection area from the entire image using image search, thereby reducing the burden on the operator in setting the matching inspection area.

[0113] <Embodiment 4> In the third embodiment, a method for generating a matching inspection region using image search has been described. However, image search and analysis take time, which may cause the operator to wait. There is a concern that the increased time required for setting may increase the setting burden on the operator.

[0114] In this embodiment, a method is described in which the operator is asked to specify the setting method at the beginning of setting the matching inspection area, thereby setting the matching inspection area more reliably and in a shorter time, thereby reducing the burden on the operator in setting the matching inspection area.

[0115] Hereinafter, the fourth embodiment will be described with respect to the differences from the first to third embodiments. Note that the parts not described in detail are the same as the first embodiment.

[0116] <Flow of generating match check area> The test setting flow in step S403 in this embodiment is as shown in the flowchart in FIG. 7. The matching test area generation flow in step S705, which is a feature of this embodiment, will be described with reference to FIG.

[0117] Reference numeral 1200 denotes a selection screen for the method of setting the coincidence inspection area. Selection screen 1200 shows five setting methods, 1201 to 1205. Image 1206 with the letter "A" written is an image of the front side, and image 1207 with the letter "B" written is an image of the back side, and each is surrounded by a dotted frame indicating that the QR code is the inspection area.

[0118] Reference numeral 1201 indicates that the positions and orientations of the coincidence inspection areas on the front and back sides are the same. Reference numeral 1202 indicates that the positions of the coincidence inspection areas on the front and back sides are symmetrical and that the orientations are the same.

[0119] Reference numeral 1203 indicates that the positions of the coincidence inspection areas on the front and back sides are point-symmetrical and the orientation is rotated by 180 degrees. Reference numeral 1204 indicates that the positions of the coincidence inspection areas on the front and back sides are manually set by an operator and the orientation is the same.

[0120] Reference numeral 1205 indicates that the positions of the coincidence inspection areas on the front and back sides are manually set by the operator, and the orientation is rotated by 180 degrees.

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

[0122] The above is the description of the flow of generating the match check area in the fourth embodiment.

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

[0124] <Embodiment 5> In the first to fourth embodiments, a method for checking the coincidence between the front and back sides has been described. Also, the coincidence check area is one on the front side and one on the back side. However, in reality, coincidence checks may be performed on multiple areas on the front or back side, or on three or more areas, such as one area on the front side and two areas on the back side.

[0125] In this embodiment, a method will be described that is not limited to the front and back, and also applicable to cases in which there are three or more coincidence inspection areas.

[0126] Hereinafter, the fifth embodiment will be described with respect to the differences from the first to fourth embodiments. Note that the parts not described in detail are the same as the first embodiment.

[0127] <Flow of generating match check area> The test setting flow in step S403 in this embodiment is as shown in the flowchart in FIG. 7. The matching test area generation flow in step S705, which is a feature of this embodiment, will be described with reference to FIG.

[0128] Reference numeral 1300 in FIG. 13(a) denotes a selection screen for selecting the type of match check, and reference numeral 1306 in FIG. 13(b) denotes a detail setting screen for setting the details of the match check.

[0129] Front and back inspection button 1301 is a selection button for a match inspection that sets one match inspection area on the front side and one on the back side. Front and back inspection (multiple) button 1302 is a selection button for setting one match inspection area on the front side, one on the back side, and one or more further match inspection areas on the front side and / or the back side.

[0130] An in-plane inspection button 1303 is a selection button for a coincidence inspection for setting two or more coincidence inspection areas within either the front or back surface.

[0131] When generating the match inspection area in step S705, the CPU 302 first displays the selection screen 1300 on the inspection setting screen 600. The display method may be a method of displaying it as an image in the area 605 or a method of displaying it as a radio button in the setting area 641.

[0132] When the front / back inspection button 1301 is selected, the CPU 302 generates one coincidence inspection area on the back side and transitions to the process of step S706. At this time, the coincidence inspection area may be generated by any of the methods described above.

[0133] When the front and back inspection (multiple) button 1302 is selected, the CPU 302 displays a detailed setting screen 1306 on the inspection setting screen 600 .

[0134] An area 1307 is a window that displays the number of coincidence check areas to be set on the front side, and the initial value is "1." An area 1308 is a window that displays the number of coincidence check areas to be set on the back side, and the initial value is "1."

[0135] Triangle button 1309 is a button for increasing the number of regions 1307, and each time it is pressed, CPU 302 increments the number of regions 1307 by 1 and redisplays it. Triangle button 1310 is a button for decreasing the number of regions 1307, and each time it is pressed, CPU 302 decrements the number of regions 1307 by 1 and redisplays it.

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

[0137] An OK button 1313 is an OK button for saving the settings on the detailed setting screen 1306 in the RAM 303 and transitioning to the inspection setting screen 600. After the OK button 1313 is pressed, the CPU 302 generates inspection areas according to the number of matching inspection areas on the front and back sides saved in the RAM 303, and displays them in the area 605. At this time, the settings of the matching inspection areas may all be the same, but displaying them so that they do not overlap makes it easier for the operator to recognize multiple matching inspection areas.

[0138] When the in-plane inspection button 1303 is selected, the CPU 302 displays a detailed setting screen 1306 on the inspection setting screen 600. At that time, if the surface displayed in area 605 is the front surface, the area 1308, triangle button 1311, and triangle button 1312 used for setting the back surface are unnecessary and are therefore grayed out. If the surface displayed in area 605 is the back surface, the area 1307, triangle button 1309, and triangle button 1310 used for setting the front surface are unnecessary and are therefore 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 is the description of the flow of generating the match check area in the fifth embodiment.

[0140] According to this embodiment, it is possible to set the coincidence check for various cases, and also to reduce the burden on the operator in setting the coincidence check area.

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

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

Claims

1. An inspection device comprising: A registration means for registering the received image as a reference image; a region setting means for setting a first region for performing a coincidence check on the reference image registered in the registration means; a generating means for generating a second area having the same settings as the first area set by the area setting means when the command for matching is received; an extracting means for extracting data from the first region and the second region from a read image obtained by reading a printed matter on which an image has been formed by an image forming means, using a reading means; a checking means for checking whether the data extracted from the first area by the extracting means matches the data extracted from the second area by the extracting means; An inspection device comprising:

2. The inspection means inspects whether the data extracted from the first area by the extraction means and the data extracted from the second area by the extraction means match pre-prepared data.

2. The inspection apparatus according to claim 1 .

3. Inspection parameters used by the extraction means and the inspection means are set in the first area set by the area setting means, and the generation means generates the second area having the same inspection parameters as the first area.

2. The inspection apparatus according to claim 1 .

4. The second area generated by the generating means is generated within the same page as the page in which the first area is set.

2. The inspection apparatus according to claim 1 .

5. The second area generated by the generating means is generated on a page different from the page on which the first area is set.

2. The inspection apparatus according to claim 1 .

6. The second area generated by the generating means is generated on a different page of the same sheet as the page on which the first area is set.

2. The inspection apparatus according to claim 1 .

7. A display unit for displaying a screen is provided. The display unit accepts changes to settings for the second area generated by the generating means.

2. The inspection apparatus according to claim 1 .

8. A display unit for displaying a screen is provided. The region setting means sets the first region in response to an operation by an operator with respect to the reference image displayed on the display unit.

2. The inspection apparatus according to claim 1 .

9. A display unit for displaying a screen is provided. When an instruction for a coincidence check is received, the front and back sides of the read image are displayed side by side on the display unit.

2. The inspection apparatus according to claim 1 .

10. When the first area displayed on the display unit is selected and a predetermined object indicating an instruction for a coincidence check is operated, the generating means generates the second area having the same settings as the first area.

10. The inspection apparatus according to claim 9.

11. A method for controlling an inspection apparatus, comprising the steps of: a registration step of registering the received image as a reference image; a region setting step of setting a first region for performing a matching test on the registered reference image; a generating step of generating a second area having the same settings as the first area when an instruction for a coincidence check is received; an inspection step of performing a coincidence inspection on a read image obtained by reading a printed matter on which an image has been formed by an image forming means, based on the first region and the second region; 13. A method for controlling an inspection apparatus comprising the steps of:

12. further comprising: extracting data from the first region and the second region; having In the inspection step, it is inspected whether the data extracted from the first region and the data extracted from the second region match each other.

12. The method for controlling an inspection apparatus according to claim 11.

Images