Information processing device, information processing method, recording system, and program

Abstract

To reduce the possibility that a detective part and a code overlap.SOLUTION: An information processing apparatus comprises code generation means which generates codes for identifying individual images of imposed image data having one or more images imposed in a recording area, candidate area determination means which determines candidate areas being candidates for arranging the codes in the recording area so that the codes are not recorded in identical positions of recording areas of individual pages of the imposed image data, recording data generation means which generates recording data based on the imposed image data so that each of the codes is arranged at least one of the candidate areas determined by the candidate area determination means, and output means which outputs the generated recording data to a recording device.SELECTED DRAWING: Figure 13

Description

[Technical Field]

[0001] This invention relates to a technique for inspecting recorded material output from a recording device. [Background technology]

[0002] In recent years, the number of recording devices that perform variable data printing has been increasing. Variable data printing refers to the continuous printing of different designs on each individual sheet without the use of printing plates.

[0003] In Patent Document 1, identification information representing the original image data to be compared is recorded on each page of the document to be inspected. The identification information is recorded in the form of a one-dimensional barcode, a two-dimensional barcode, or numerical data (hereinafter collectively referred to as a code), and the quality of the document is inspected by reading the code at the same time as reading the document to be inspected, and comparing it with the original data in association with the code. [Prior art documents] [Patent Documents]

[0004] [Patent Document 1] Japanese Patent Publication No. 2011-248577 [Overview of the Initiative] [Problems that the invention aims to solve]

[0005] Defects can occur in recorded materials due to various factors related to the device. In particular, malfunctions occurring in specific locations on the device may persist as image defects in fixed positions on the recording medium. If the location where defects persist overlaps with the location where codes for variable data inspection are embedded, there is a risk that the inspection cannot be performed correctly.

[0006] Therefore, the present invention aims to reduce the possibility of the defective portion and the code overlapping. [Means for solving the problem]

[0007] An information processing apparatus according to one aspect of the present invention includes: a code generation means for generating a code for identifying each image in imposed image data in which one or more images are imposed on a recording area; a candidate area determination means for determining candidate areas for which the code is to be placed in the recording area, such that the code is not recorded in the same position in the recording area of ​​each page of a plurality of imposed image data; a recording data generation means for generating recording data based on the imposed image data such that the code is placed in at least one of the candidate areas determined by the candidate area determination means; and an output means for outputting the generated recording data to a recording device. The candidate region determination means excludes from the candidate regions regions regions regions that have been determined to be defective regions by a sensor that checks the recording status, which is obtained from the recording device. It is characterized by the following: [Effects of the Invention]

[0008] According to the present invention, the possibility of the defective portion overlapping with the code can be reduced. [Brief explanation of the drawing]

[0009] [Figure 1] This is an overview diagram of the recording system. [Figure 2] This is a perspective view of the recording unit. [Figure 3] This is an explanatory diagram of the displacement patterns of the recording unit. [Figure 4] This is a block diagram of the control system for the recording system. [Figure 5] This is a block diagram of the control system for the recording system. [Figure 6] This is an explanatory diagram illustrating an example of the recording system's operation. [Figure 7] This is an explanatory diagram illustrating an example of the recording system's operation. [Figure 8] This diagram shows the nozzle arrangement of the recording head. [Figure 9] This is a flowchart illustrating the processing in the image processing unit. [Figure 10] This is a flowchart explaining the processing in the inspection department. [Figure 11] This is a flowchart of the manuscript data generation process. [Figure 12] An example of the generated page attachment data. [Figure 13] A flowchart of code embedding position determination. [Figure 14] An explanatory diagram of each step of the embedding position determination flow on the first page. [Figure 15] A flowchart of the grid narrowing process. [Figure 16] An explanatory diagram of each step of the embedding position determination flow on the second page. [Figure 17] A flowchart of the manuscript data generation process. [Figure 18] An example of the generated page attachment data. [Figure 19] A flowchart of the manuscript data generation process. [Figure 20] An example of the generated page attachment data. [Figure 21] An explanatory diagram of each step of the embedding position determination flow on the first page. [Figure 22] A flowchart of the analysis performed in the code analysis unit.

Mode for Carrying Out the Invention

[0010] <<Embodiment 1>> Embodiments of the present invention will be described with reference to the drawings. In each figure, arrows X and Y indicate the horizontal direction and are perpendicular to each other. Arrow Z indicates the vertical direction.

[0011] <Recording System> FIG. 1 is a front view schematically showing a recording system 1 according to an embodiment of the present invention. The recording system 1 is a sheet-fed inkjet printer that manufactures a recording object P' by transferring an ink image onto a recording medium P via a transfer body 2. The recording system 1 includes a recording device 1A and a transport device 1B. In the present embodiment, the X direction, Y direction, and Z direction respectively indicate the width direction (total length direction), depth direction, and height direction of the recording system 1. The recording medium P is transported in the X direction.

[0012] Furthermore, "recording" includes not only cases where meaningful information such as characters and figures is formed, but also broadly cases where images, patterns, etc. are formed on a recording medium, or where the medium is processed, regardless of whether it is meaningful or not, and does not depend on whether or not it is manifested in a way that can be perceived visually by humans.In addition, in this embodiment, a sheet of paper is assumed as the "recording medium," but it may also be cloth, plastic film, etc.

[0013] There are no particular limitations on the ink's composition, but in this embodiment, we assume the use of an aqueous pigment ink containing a colorant, water, and resin.

[0014] <Recording device> The recording device 1A includes a recording unit 3, a transfer unit 4, peripheral units 5A to 5D, and a supply unit 6.

[0015] <Recording Unit> The recording unit 3 includes a plurality of recording heads 30 and a carriage 31. See Figures 1 and 2. Figure 2 is a perspective view of the recording unit 3. The recording heads 30 eject liquid ink onto the transfer body 2, forming an ink image of the recording image on the transfer body 2.

[0016] In this embodiment, each recording head 30 is a full-line head extending in the Y direction, and nozzles are arranged to cover the width of the image placement area of ​​the largest usable recording medium. The recording head 30 has an ink ejection surface on its lower surface, through which nozzles are opened, and the ink ejection surface faces the surface of the transfer body 2 via a small gap (e.g., several mm). Figure 8 shows the nozzle arrangement of the recording head 30. As shown in the figure, the recording head 30 has multiple ejection substrates 301, 302, 303, 304… arranged in an overlapping manner in the Y direction. Each ejection substrate has eight rows of nozzles a to h arranged in the nozzle arrangement direction. The nozzle spacing in the Y direction of each nozzle row is 1200 dpi. Here, nozzle rows a to h are arranged with a 1 / 4 offset of 1200 dpi in the X direction. The ejection substrates 301, 302, 303, 304… are arranged along the nozzle arrangement direction, and multiple recording heads 30 with similar nozzle arrangements are arranged in a direction that intersects the nozzle arrangement direction. Then, an image is recorded by ejecting multiple colors of ink onto corresponding areas on the recording medium. In this embodiment, since the transfer body 2 moves cyclically along a circular orbit, the multiple recording heads 30 are arranged radially.

[0017] Each nozzle is equipped with an ejection element. The ejection element is, for example, an element that generates pressure inside the nozzle to eject the ink, and the technology of inkjet heads in known inkjet printers can be applied. Examples of ejection elements include elements that eject ink by causing film boiling in the ink and forming bubbles using an electro-thermal converter, elements that eject ink using an electro-mechanical converter, and elements that eject ink using static electricity. From the viewpoint of high-speed, high-density recording, an ejection element using an electro-thermal converter can be used.

[0018] In this embodiment, nine recording heads 30 are provided. Each recording head 30 ejects a different type of ink. Different types of ink are, for example, inks with different colorants, such as yellow ink, magenta ink, cyan ink, and black ink. One recording head 30 ejects one type of ink, but a single recording head 30 may eject multiple types of ink. When multiple recording heads 30 are provided in this way, some of them may eject ink that does not contain colorants (for example, clear ink).

[0019] The carriage 31 supports multiple recording heads 30. Each recording head 30 has its ink ejection surface end fixed to the carriage 31. This allows for a more precise maintenance of the gap between the ink ejection surface and the transfer body 2. The carriage 31 is configured to be displaceable while mounting the recording heads 30, guided by guide members RL. In this embodiment, the guide members RL are rail members extending in the Y direction and are provided in pairs spaced apart in the X direction. Slide portions 32 are provided on each side of the carriage 31 in the X direction. The slide portions 32 engage with the guide members RL and slide along the guide members RL in the Y direction.

[0020] <Transfer Unit> The transfer unit 4 will be described with reference to Figure 1. The transfer unit 4 includes a transfer drum (transfer cylinder) 41 and an impression cylinder 42. These cylinders are rotating bodies that rotate around a rotation axis in the Y direction and have a cylindrical outer surface. In Figure 1, the arrows shown in the respective figures of the transfer drum 41 and impression cylinder 42 indicate their rotation directions, with the transfer drum 41 rotating clockwise and the impression cylinder 42 rotating counterclockwise.

[0021] The transfer drum 41 is a support that supports the transfer body 2 on its outer circumferential surface. The transfer body 2 (intermediate transfer body) is provided on the outer circumferential surface of the transfer drum 41, either continuously or intermittently in the circumferential direction. When provided continuously, the transfer body 2 is formed in an endless strip shape. When provided intermittently, the transfer body 2 is formed in an ended strip shape divided into multiple segments, and each segment can be arranged in an arc shape at equal pitches on the outer circumferential surface of the transfer drum 41.

[0022] As the transfer drum 41 rotates, the transfer body 2 moves cyclically along a circular orbit. Depending on the rotational phase of the transfer drum 41, the position of the transfer body 2 can be distinguished into pre-discharge processing area R1, discharge area R2, post-discharge processing areas R3 and R4, transfer area R5, and post-transfer processing area R6. The transfer body 2 passes through these areas cyclically.

[0023] The pre-discharge processing area R1 is the area where pre-processing is performed on the transfer body 2 before ink is ejected by the recording unit 3, and is the area where processing is performed by the peripheral unit 5A. In this embodiment, a reaction solution is applied. The discharge area R2 is the formation area where the recording unit 3 ejects ink onto the transfer body 2 to form an ink image. The post-discharge processing areas R3 and R4 are processing areas where processing is performed on the ink image after ink ejection, with the post-discharge processing area R3 being the area where processing is performed by the peripheral unit 5B, and the post-discharge processing area R4 being the area where processing is performed by the peripheral unit 5C. The transfer area R5 is the area where the ink image on the transfer body 2 is transferred to the recording medium P by the transfer unit 4. The post-transfer processing area R6 is the area where post-processing is performed on the transfer body 2 after transfer, and is the area where processing is performed by the peripheral unit 5D.

[0024] In this embodiment, the discharge region R2 is a region with a certain interval. The other regions R1, R3 to R6 have narrower intervals compared to the discharge region R2. To use a clock face analogy, in this embodiment, the pre-discharge processing region R1 is roughly at the 10 o'clock position, the discharge region R2 is roughly in the range from 11 o'clock to 1 o'clock, the post-discharge processing region R3 is roughly at the 2 o'clock position, and the post-discharge processing region R4 is roughly at the 4 o'clock position. The transfer region R5 is roughly at the 6 o'clock position, and the post-transfer processing region R6 is roughly in the 8 o'clock position.

[0025] The impression cylinder 42 is pressed against the transfer body 2 by its outer surface. The outer surface of the impression cylinder 42 is provided with at least one grip mechanism for holding the leading edge of the recording medium P. Multiple grip mechanisms may be provided spaced apart in the circumferential direction of the impression cylinder 42. As the recording medium P is transported in close contact with the outer surface of the impression cylinder 42, the ink image on the transfer body 2 is transferred as it passes through the nip portion between the impression cylinder 42 and the transfer body 2.

[0026] The drive source, such as a motor, that drives the transfer drum 41 and the impression cylinder 42 is common to both, and the driving force can be distributed by a transmission mechanism such as a gear mechanism.

[0027] <Peripheral Units> The peripheral units 5A to 5D are arranged around the transfer drum 41. In this embodiment, the peripheral units 5A to 5D are, in order, a transfer unit, an absorption unit, a heating unit, and a cleaning unit.

[0028] The application unit 5A is a mechanism that applies the reaction solution onto the transfer body 2 before the ink is ejected by the recording unit 3. The reaction solution is a liquid containing components that increase the viscosity of the ink. Here, increasing the viscosity of the ink means that the colorants, resins, etc. that make up the ink come into contact with the components that increase the viscosity of the ink and react chemically or are physically adsorbed, resulting in an increase in the viscosity of the ink. This increase in ink viscosity includes not only cases where the viscosity of the entire ink increases, but also cases where a local increase in viscosity occurs due to the aggregation of some of the components that make up the ink, such as colorants and resins.

[0029] The components used to increase the viscosity of the ink are not particularly limited, but can include metal ions, polymer flocculants, etc., and can be substances that cause a change in the pH of the ink and cause the colorants in the ink to aggregate, and organic acids can be used. Examples of mechanisms for applying the reaction solution include rollers, recording heads, die coating devices (die coaters), and blade coating devices (blade coaters). If the reaction solution is applied to the transfer body 2 before the ink is dispensed onto the transfer body 2, the ink that reaches the transfer body 2 can be fixed immediately. This suppresses bleeding, which is caused by adjacent inks mixing together.

[0030] The absorption unit 5B is a mechanism that absorbs liquid components from the ink image on the transfer medium 2 before transfer. By reducing the liquid component of the ink image, blurring and other issues in the image recorded on the recording medium P can be suppressed. From a different perspective, the reduction of liquid components can also be described as concentrating the ink that makes up the ink image on the transfer medium 2. Concentrating the ink means that the proportion of solid components such as colorants and resins contained in the ink relative to the liquid component increases as the liquid component of the ink decreases.

[0031] The absorption unit 5B includes, for example, a liquid absorbent member that contacts the ink image to reduce the amount of liquid component in the ink image. The liquid absorbent member may be formed on the outer circumferential surface of the roller, or it may be formed in an endless sheet shape and run circulatingly. In terms of protecting the ink image, the movement speed of the liquid absorbent member may be the same as the peripheral speed of the transfer body 2, so that the liquid absorbent member moves in synchronization with the transfer body 2.

[0032] The liquid absorbent member may include a porous body that comes into contact with the ink image. To suppress the adhesion of solid ink particles to the liquid absorbent member, the pore size of the porous body on the surface in contact with the ink image may be 10 μm or less. Here, pore size refers to the average diameter and can be measured by known means, such as the mercury intrusion method, nitrogen adsorption method, or SEM image observation. The liquid component is not particularly limited as long as it does not have a fixed shape, is fluid, and has a nearly constant volume. For example, water and organic solvents contained in ink or reaction solutions can be cited as liquid components.

[0033] The heating unit 5C is a mechanism that heats the ink image on the transfer medium 2 before transfer. By heating the ink image, the resin in the ink image melts, improving the transferability to the recording medium P. The heating temperature can be set to or above the minimum film-forming temperature (MFT) of the resin. The MFT can be measured using generally known methods, such as devices conforming to JIS K 6828-2:2003 or ISO 2115:1996. From the viewpoint of transferability and image robustness, the heating temperature may be 10°C or more higher than the MFT, and even 20°C or more higher. The heating unit 5C can use known heating devices such as various lamps such as infrared lamps and hot air fans. In terms of heating efficiency, an infrared heater can be used.

[0034] The cleaning unit 5D is a mechanism for cleaning the transfer body 2 after the transfer. The cleaning unit 5D removes any ink remaining on the transfer body 2, as well as any debris on the transfer body 2. The cleaning unit 5D can appropriately use known transfer methods, such as a method of bringing a porous member into contact with the transfer body 2, a method of rubbing the surface of the transfer body 2 with a brush, or a method of scraping the surface of the transfer body 2 with a blade. In addition, the cleaning member used for cleaning can be of a known shape, such as a roller shape or a web shape.

[0035] As described above, this embodiment includes an ink application unit 5A, an absorption unit 5B, a heating unit 5C, and a cleaning unit 5D as peripheral units. However, some of these units may be given a cooling function for the transfer body 2, or an additional cooling unit may be added. In this embodiment, the temperature of the transfer body 2 may rise due to the heat from the heating unit 5C. After the recording unit 3 ejects ink onto the transfer body 2, if the ink image exceeds the boiling point of water, which is the main solvent of the ink, the absorption performance of the liquid component by the absorption unit 5B may decrease. By cooling the transfer body 2 so that the ejected ink remains below the boiling point of water, the absorption performance of the liquid component can be maintained.

[0036] The cooling unit may be a blowing mechanism that blows air onto the transfer body 2, or a mechanism that brings a component (e.g., a roller) into contact with the transfer body 2 and cools this component by air or water. It may also be a mechanism that cools the cleaning component of the cleaning unit 5D. The cooling timing may be the period after transfer and before the application of the reaction solution.

[0037] <Supply Unit> The supply unit 6 is a mechanism that supplies ink to each recording head 30 of the recording unit 3. The supply unit 6 may be located on the rear side of the recording system 1. The supply unit 6 includes a storage section TK for storing ink for each type of ink. The storage section TK may consist of a main tank and a sub-tank. Each storage section TK and each recording head 30 are connected by a flow path 6a, and ink is supplied from the storage section TK to the recording head 30. The flow path 6a may be a flow path that circulates ink between the storage section TK and the recording head 30, and the supply unit 6 may be equipped with a pump or the like for circulating the ink. A degassing mechanism for removing air bubbles from the ink may be provided in the flow path 6a or in the storage section TK. A valve for adjusting the liquid pressure of the ink and atmospheric pressure may be provided in the flow path 6a or in the storage section TK. The heights of the storage unit TK and the recording head 30 in the Z direction may be designed such that the ink level in the storage unit TK is lower than the ink ejection surface of the recording head 30.

[0038] <Conveying device> The transport device 1B is a device that feeds the recording medium P to the transfer unit 4 and discharges the recorded material P' with the ink image transferred from the transfer unit 4. The transport device 1B includes a feeding unit 7, a plurality of transport cylinders 8, 8a, two sprockets 8b, a chain 8c, and a recovery unit 8d. In Figure 1, the inner arrows of the figures for each component of the transport device 1B indicate the rotation direction of that component, and the outer arrows indicate the transport path of the recording medium P or recorded material P'. The recording medium P is transported from the feeding unit 7 to the transfer unit 4, and the recorded material P' is transported from the transfer unit 4 to the recovery unit 8d. The side of the feeding unit 7 is sometimes called the upstream side in terms of the transport direction, and the side of the recovery unit 8d is sometimes called the downstream side.

[0039] The feeding unit 7 includes a loading section on which multiple recording media P are stacked, and a feeding mechanism that feeds recording media P one by one from the loading section to the upstream transport cylinder 8. Each transport cylinder 8, 8a is a rotating body that rotates around a rotation axis in the Y direction and has a cylindrical outer surface. At least one grip mechanism for holding the leading edge of a recording media P (or recording P') is provided on the outer surface of each transport cylinder 8, 8a. The gripping and releasing operations of each grip mechanism are controlled so that recording media P are transferred between adjacent transport cylinders.

[0040] The two transport cylinders 8a are for reversing the recording medium P. When recording on both sides of the recording medium P, after the transfer to the front side, the recording medium P is not passed from the impression cylinder 42 to the adjacent downstream transport cylinder 8, but to the transport cylinders 8a. The recording medium P is reversed front to back via the two transport cylinders 8a, and is then passed back to the impression cylinder 42 via the transport cylinder 8 upstream of the impression cylinder 42. As a result, the back side of the recording medium P faces the transfer drum 41, and the ink image is transferred to the back side.

[0041] The chain 8c is wound between two sprockets 8b. One of the two sprockets 8b is a drive sprocket and the other is a driven sprocket. The rotation of the drive sprocket causes the chain 8c to move cyclically. The chain 8c is provided with multiple gripping mechanisms spaced apart along its longitudinal direction. The gripping mechanisms grasp the end of the recording object P'. The recording object P' is passed from the transport drum 8 located at the downstream end to the gripping mechanisms of the chain 8c, and the gripped recording object P' is transported to the retrieval unit 8d by the movement of the chain 8c, where the grip is released. As a result, the recording object P' is loaded into the retrieval unit 8d.

[0042] <Post-processing unit> The transport device 1B is equipped with post-processing units 10A and 10B. The post-processing units 10A and 10B are located downstream of the transfer unit 4 and are mechanisms for performing post-processing on the recording material P'. Post-processing unit 10A performs processing on the surface of the recording material P', and post-processing unit 10B performs processing on the back surface of the recording material P'. Examples of processing include coating the image recording surface of the recording material P' for purposes such as image protection and glossing. Examples of coatings include liquid application, sheet welding, lamination, etc.

[0043] <Inspection Unit> The transport device 1B is equipped with inspection units 9A and 9B. Inspection units 9A and 9B are located downstream of the transfer unit 4 and are mechanisms for inspecting the recorded material P'.

[0044] In this embodiment, the inspection unit 9A is an imaging device that captures images recorded on the recording material P', and includes, for example, an image sensor such as a CCD sensor or a CMOS sensor. The inspection unit 9A captures recorded images during the continuously performed recording operation. Based on the images captured by the inspection unit 9A, it is possible to check changes over time such as the color of the recorded image and determine whether or not correction of the image data or recorded data is possible. In this embodiment, the inspection unit 9A is set to have an imaging range that can capture the entire surface of the recording material P'.

[0045] In this embodiment, the inspection unit 9B is also an imaging device that captures images recorded on the recording object P', and includes, for example, an image sensor such as a CCD sensor or a CMOS sensor. The inspection unit 9B captures the recorded image during the test recording operation. The inspection unit 9B captures the entire recorded image, and based on the image captured by the inspection unit 9B, basic settings for various corrections related to the recorded data can be made. In this embodiment, the inspection unit 9B is positioned to capture the recording object P' being transported by the chain 8c. When the inspection unit 9B captures the recorded image, the movement of the chain 8c is temporarily stopped and the entire chain is captured. The inspection unit 9B may also be a scanner that scans the recording object P'.

[0046] <Control Unit> Next, the control unit of the recording system 1 will be described. Figures 4 and 5 are block diagrams of the control unit 13 of the recording system 1. The control unit 13 is communicatively connected to the higher-level device (DFE) HC2, and the higher-level device HC2 is communicatively connected to the host device HC1.

[0047] In the host device HC1, the source data for the recorded images is generated or saved. This source data is generated in the form of electronic files, such as document files or image files. During the generation of this source data, an inspection code used for checking the data's recording process is embedded within the resulting source data. The method for embedding the code will be described in detail in the embodiments described later.

[0048] This document data is transmitted to the host device HC2, which converts the received document data into a data format usable by the control unit 13 (for example, RGB data that represents an image using RGB). The converted data is then transmitted as image data from the host device HC2 to the control unit 13, and the control unit 13 starts recording based on the received image data.

[0049] In this embodiment, the control unit 13 is broadly divided into a main controller 13A and an engine controller 13B. The main controller 13A includes a processing unit 131, a storage unit 132, an operation unit 133, an image processing unit 134, a communication interface 135, a buffer 136 and a communication interface 137, and an inspection unit 138.

[0050] The processing unit 131 is a processor such as a CPU, which executes programs stored in the memory unit 132 and controls the entire main controller 13A. The memory unit 132 is a storage device such as RAM, ROM, hard disk, or SSD, which stores programs and data executed by the CPU 131 and also provides a work area for the CPU 131. The operation unit 133 is an input device such as a touch panel, keyboard, or mouse, which receives user instructions.

[0051] The image processing unit 134 is, for example, an electronic circuit having an image processing processor. The buffer 136 is, for example, RAM, a hard disk, or an SSD. The communication interface 135 communicates with the host device HC2, and the communication interface 137 communicates with the engine controller 13B. In Figure 4, the dashed arrows illustrate the flow of image data processing. Image data received from the host device HC2 via the communication interface 135 is stored in the buffer 136. The image processing unit 134 reads the image data from the buffer 136, applies predetermined image processing to the read image data, and stores it back in the buffer 136. The processed image data stored in the buffer 136 is transmitted to the engine controller 13B via the communication interface 137 as recording data used by the print engine.

[0052] Figure 9 is a flowchart illustrating the processing in the image processing unit 134. The input unit 901 receives image data transmitted from the buffer 136 and passes it to the image processing unit 134. This image processing unit 134 consists of an ink color conversion processing unit 902, an HS (Head Shading) processing unit 903, a tone curve correction unit 904, and a quantization processing unit 905. The input unit 901 receives RGB data from the host device HC2. The input RGB data is 8 bits each of image data (R, G, B) in the color reproduction area of ​​the recording device 1A, with a resolution of 600 dpi.

[0053] The ink color conversion processing unit 902 converts the input 8-bit (R, G, B) image data into image data for the inks used by the recording device 1A. In this embodiment, the recording device 1A uses black (K), cyan (C), magenta (M), and yellow (Y) inks, and the RGB signal image data is converted into image data consisting of 8-bit color signals for K, C, M, and Y. This color conversion is performed by known methods such as matrix arithmetic processing or processing using a three-dimensional lookup table. In this embodiment, a three-dimensional lookup table is used, and interpolation is used in combination with it to perform the conversion processing. Alternatively, the processing in the ink color conversion processing unit 902 may be performed before input to the input unit 901. In that case, 8-bit image data for K, C, M, and Y will be input to the input unit 901.

[0054] The Head Shading (HS) processing unit 903 receives 8-bit color signals for each of the K, C, M, and Y colors and converts 8-bit data for each ink color into image data of the ink color signal according to the characteristics of each nozzle constituting the recording head, such as the amount of ink ejected. This converts the data into image data that allows for uniform recording in accordance with the density unevenness caused by the characteristics of each nozzle, such as the amount of ink ejected. In this embodiment, processing is performed using a one-dimensional lookup table.

[0055] The tone curve correction unit 904 adjusts the number of dots recorded by the output unit 906 for each ink color in the image data consisting of each 8-bit ink color signal processed by HS. The relationship between the number of dots recorded on the recording medium and brightness may not be linear, so the tone curve correction unit 904 corrects each 8-bit image data to make this relationship linear and adjusts the number of dots recorded on the recording medium.

[0056] The quantization processing unit 905 performs quantization on the 8-bit ink color image data processed by the tone curve correction unit 904 to obtain 1-bit binary data. In this embodiment, it first converts the data into 3-bit, 5-value index data for each ink color, from 0 to 4. This index data 0 to 4 corresponds to a pattern in which 0 to 4 dots are arranged in a 2x2 pixel array with a resolution of 1200 dpi. The form of the quantization processing unit 905 is not limited to this example. For example, it may be a form in which the 8-bit image data is directly binarized to obtain whether or not ink is ejected. Furthermore, although this embodiment uses the dithering method as the quantization method, other quantization methods such as error diffusion may be used.

[0057] The output unit 906 drives the recording head based on the dot data obtained by quantization and ejects ink of each color onto the recording medium to perform recording. Specifically, the output unit 906 is composed of the recording system 1 shown in Figure 1. The inspection unit 138 is an inspection processing unit that inspects the recorded material P'.

[0058] Figure 10 is a flowchart illustrating the processing in the inspection unit 138. The inspection image input unit 1001 inputs the image (hereinafter referred to as the inspection image) taken by the aforementioned inspection unit 9A to the inspection unit 138. The inspection image is an image of the record object P' to be inspected. The code analysis unit 1002 obtains the area of ​​the inspection code from the input inspection image and performs analysis. The area of ​​the code can be obtained using existing technologies such as pattern matching. The code analysis is performed using a predetermined existing technology according to the code standard. Then, information represented by numbers or letters embedded in the code is obtained. This information represents the identifier of the original data of the record object P' to be inspected.

[0059] The comparison data matching unit 1003 uses the information acquired by the code analysis unit 1002 to acquire the original data of the record P' to be inspected. Then, after applying predetermined image processing to both the inspection image and the original data, a comparison is performed, and any region where a difference exceeding a predetermined standard is detected is determined to be defective. The comparison method may, for example, be to find the difference in signal values ​​of corresponding pixels in the inspection image and the original data, or to calculate feature quantities including color and shape and find the difference in corresponding regions. Alternatively, without setting a predetermined standard, the inspection image and original data may be input into a pre-trained machine learning model to determine the defective region. The original data compared with the inspection image may be data after the code has been embedded, or data before the code has been embedded.

[0060] The inspection result output unit 1005 displays the inspection results on a display screen such as a monitor (not shown) to inform the person operating the recording system 1. If necessary, it also transmits the inspection results to the host device HC1, the storage unit 132, the engine controller 13B, etc.

[0061] As shown in Figure 5, the engine controller 13B includes control units 14, 15A to 15E, and acquires detection results from the sensor group and actuator group 16 of the recording system 1 and performs drive control. Each of these control units includes a processor such as a CPU, a storage device such as RAM or ROM, and an interface with external devices. Note that the division of the control units is just an example, and some controls may be performed by multiple control units that are further subdivided, or conversely, multiple control units may be integrated and configured to perform their control contents in a single control unit.

[0062] The engine control unit 14 controls the entire engine controller 13B. The recording control unit 15A converts the recording data received from the main controller 13A into a data format suitable for driving the recording heads 30, such as raster data. The recording control unit 15A controls the ejection of each recording head 30.

[0063] The transfer control unit 15B controls the application unit 5A, the absorption unit 5B, the heating unit 5C, and the cleaning unit 5D.

[0064] The reliability control unit 15C controls the supply unit 6, the recovery unit 12, and the drive mechanism that moves the recording unit 3 between the discharge position POS1 and the recovery position POS3. The transport control unit 15D controls the drive of the transfer unit 4 and the transport device 1B. The inspection control unit 15E controls the inspection unit 9B and the inspection unit 9A. Of the sensor group and actuator group 16, the sensor group includes sensors that detect the position and speed of movable parts, sensors that detect temperature, and image sensors. The actuator group includes motors, electromagnetic solenoids, electromagnetic valves, and the like.

[0065] <Example of operation> Figure 6 schematically shows an example of the recording operation. The following steps are performed cyclically while the transfer drum 41 and impression cylinder 42 are rotated. As shown in state ST1, the reaction liquid L is first applied to the transfer body 2 from the application unit 5A. The area on the transfer body 2 to which the reaction liquid L has been applied moves as the transfer drum 41 rotates. When the area to which the reaction liquid L has been applied reaches below the recording head 30, ink is ejected from the recording head 30 onto the transfer body 2 as shown in state ST2. This forms an ink image IM. At this time, the ejected ink mixes with the reaction liquid L on the transfer body 2, promoting the aggregation of the colorant. The ejected ink is supplied to the recording head 30 from the storage unit TK of the supply unit 6.

[0066] The ink image IM on the transfer body 2 moves as the transfer body 2 rotates. When the ink image IM reaches the absorption unit 5B, the liquid component is absorbed from the ink image IM by the absorption unit 5B, as shown in state ST3. When the ink image IM reaches the heating unit 5C, the ink image IM is heated by the heating unit 5C, as shown in state ST4, the resin in the ink image IM melts, and the ink image IM is formed into a film. The recording medium P is transported by the transport device 1B in synchronization with the formation of this ink image IM.

[0067] As shown in state ST5, the ink image IM and the recording medium P reach the nip portion between the transfer body 2 and the impression cylinder 42, the ink image IM is transferred to the recording medium P, and a recording P' is produced. After passing through the nip portion, the image recorded on the recording P' is captured by the inspection unit 9A and the recorded image is inspected. The recording P' is transported to the recovery unit 8d by the transport device 1B.

[0068] The portion of the transfer body 2 where the ink image IM was formed is cleaned by the cleaning unit 5D upon reaching the cleaning unit 5D, as shown in state ST6. After cleaning, the transfer body 2 has completed one rotation, and the transfer of the ink image to the recording medium P is repeated using the same procedure. In the above explanation, for the sake of ease of understanding, it has been described as if the transfer of the ink image IM to one recording medium P is performed once per rotation of the transfer body 2, but the transfer of the ink image IM to multiple recording mediums P can be performed continuously per rotation of the transfer body 2.

[0069] As this recording operation continues, maintenance of each recording head 30 becomes necessary. Figure 7 shows an example of the operation during maintenance of each recording head 30. State ST11 indicates that the recording unit 3 is located at the ejection position POS1. State ST12 indicates that the recording unit 3 is passing through the reserve recovery position POS2, during which time the recovery unit 12 performs a process to restore the ejection performance of each recording head 30 of the recording unit 3. Subsequently, as shown in state ST13, with the recording unit 3 located at the recovery position POS3, the recovery unit 12 performs a process to restore the ejection performance of each recording head 30.

[0070] <Code generation process> The system configuration of the host device HC1 in this embodiment will be explained with reference to Figure 4. The host device HC1 has a code generation unit 201, a recording data generation unit 202, a candidate area determination unit 203, and a storage unit 204. The code generation unit 201 generates a test code. The recording data generation unit 202 combines the code generated by the code generation unit 201 with imposition data in which images are imposed on the recording area. That is, it embeds the code into the imposition data. The candidate area determination unit 203 determines the position in which the test code is embedded. The storage unit 204 is a storage device such as RAM, ROM, hard disk, or SSD, and stores programs or data executed by the CPU of the host device HC1, or provides a work area to the CPU.

[0071] Figure 11 illustrates the flow of the process for generating document data with embedded inspection codes, as performed by the host device HC1 in this embodiment. This flow is executed by the code generation unit 201, the recording data generation unit 202, or the candidate area determination unit 203 of the host device HC1. That is, it is realized by the CPU of the host device HC1 loading a program stored in the ROM of the host device HC1 into RAM and executing it. The symbol "S" in the description of each process indicates a step in the flowchart. When the host device HC1 starts the document data generation process, it generates imposition data for the images to be recorded in S1101. The generation of imposition data will now be explained.

[0072] Figure 12 shows an example of imposition data generated in this embodiment. Imposition data is data in which one or more images are pasted onto one page, as shown in D1 to D15 in Figure 12. One inspection code is embedded in each page of this imposition data. The embedded code contains information about the original data used for comparison when inspecting the quality of the imposition data, and the imposition data and the original data are linked by the embedded code. In this embodiment, the first page of data D1 has four images, images 11, 12, 13, and 14, all of the same size and aligned and imposed. The images imposed on a single page may be the same or different. Images 11, 12, 13, and 14 imposed on the first page are cut into four pieces so that each imposition data remains before or after comparison with the original data. Similarly, other pages are cut so that only the imposition data portion remains. The second page of data D2 has only image 21 imposed in the center. On page 3, data D3 contains images 31 and 32. The last page is page 15, and on page 15, data D15 contains images 151 and 152. Here, the vertical and horizontal dimensions of data D1, D2, D3...D15 are assumed to be the dimensions of the recording medium P loaded in the feed unit 7.

[0073] Returning to the explanation of Figure 11, in S1102, the host device HC1 obtains the number of pages M in the imposition data. In this embodiment, as shown in Figure 12, M = 15. In S1103, the host device HC1 starts the process of embedding an inspection code into the first page of the document, with m = 1 as the page to be processed.

[0074] In S1104, the host device HC1 generates an inspection code to be embedded in the data D1 on the first page. The information that forms the basis of the generated code is the identification value of the data D1 on the first page. The identification value may be, for example, a name that identifies the image itself, or an address on the storage unit 132 that stores the information. Also, as mentioned above, in the case of imposed data in which multiple images are pasted on one page, one identification value can also be used as metadata for the information of the multiple images that are imposed. For example, in the following, four images are imposed on D1, but it means that there is one identification value for the data in the state in which the four images are imposed.

[0075] Here, it is desirable to ensure a sufficient number of digits for the identification value of each page, taking into account the number of pages in the imposition data generated in S1101. For example, since the number of pages M in the imposition data in this embodiment is 15 pages, at least two digits should be ensured for the identification value. For example, it is good to set the identification value of data D1 on the first page to "01". Alternatively, one may ensure the assumed maximum number of pages for the job sent to the recording device and set it to, for example, six digits, "000001". In this embodiment, the identification value of data D1 on the first page is set to "000001". In this embodiment, the NW-7 standard is used for the method of converting "000001", the identification value of data D1 on the first page, into a code. NW-7 is a representative code standard that can encode numbers and predetermined symbols. The code standard is not limited to NW-7; ITF (Interleaved Two of Five), CODE39, or CODE128 may also be used. Depending on the standard used, there are different constraints such as the symbols, alphabets, and number of digits that can be used in addition to numbers. It is advisable to choose the appropriate code based on the content and size of the information to be included. Alternatively, instead of a one-dimensional code as described above, a two-dimensional code such as a QR (Quick Response) code (registered trademark) may be chosen. In any case, it is preferable that the size of the code created meets the size recommended by each standard.

[0076] In S1105, the host device HC1 determines the embedding position of the code. Details of the method for determining the embedding position of the code will be described later using Figure 13. In S1106, the host device HC1 performs image synthesis using the code generated in S1104 and data D1. That is, the generated code is embedded in data D1 on page m=1. Here, the position where the code is embedded is the coordinates determined in S1105.

[0077] In S1107, the host device HC1 sets the number of pages to be processed to m=m+1 and begins the process of embedding a verification code on the second page. In S1108, the host device HC1 determines whether the number of pages to be processed, m, has reached the number of pages already acquired, M. That is, it checks whether processing for 15 pages has been completed. Since this is the step where processing for the second page has started, it returns to S1104 to generate the code to be embedded on the second page. The code to be embedded on the second page is generated from the identification value "000002" of data D2 on the second page in Figure 12. The process of embedding a code on each page of the original data is repeated in the same manner until m=15.

[0078] In S1108, the host device HC1 terminates the flow when it determines that m=M, i.e., that processing has been completed for all acquired pages. Up to this point, one code can be embedded in each of the 15 pages of the imposition data.

[0079] Figure 13 is an explanatory diagram of the flow for determining the code embedding location in S1105. Specifically, it explains the case of determining the location for data D1 on the first page of Figure 12. This flow is realized when the CPU expands the program stored in the program memory of the host device HC1 into the data memory and executes it. The symbol "S" in the explanation of each process means a step in that flowchart. When device HC1 starts the process of determining the code embedding location, in S1301 it sets a candidate area R for the code embedding location. A candidate area is a candidate area for embedding an identifier.

[0080] Figure 14 illustrates the state of candidate regions at each step of the code embedding location determination flow in Figure 13. Figure 14 illustrates candidate regions using data D1 from Figure 12 as an example. Figure 14(a) shows R when candidate region R is at its maximum. max This is an example. The maximum R of the candidate region R. max This is the recordable area specific to the recording device when set to the outermost part within a range smaller than the recording medium P. That is, the code is R maxIt cannot be embedded further outwards. Fig. 14(b) shows an example of R when the candidate region R is at its minimum. min The minimum R of the candidate region R min is the region closest to the image placement region (hereinafter referred to as the image region), which is the region where the image is placed, among the ranges outside the image region. Since the code may cause an error during inspection if it overlaps with the image region, it is embedded at a position that is a certain distance away from the image region. Also, although it is possible to embed the code near the image region or between a plurality of images affixed within the image region, it is not desirable to embed the code at those positions because the code and the image may overlap due to reasons such as a deviation in the ejection timing. The image region IM of the affixed data marked with a thick dashed line is the image region when images 11, 12, 13, and 14 are regarded as one image. The minimum R of the candidate region R min sets the lengths of both ends in the Y direction of IM to a and both ends in the X direction to b outside respectively. Assuming that the code generated in S1104 has a width of 20 mm in the Y direction and a width of 10 mm in the X direction, the region where a = 20 mm and b = 10 mm is the minimum R of the candidate region R min As explained in Figs. 14(a) and (b), the candidate region R is preferably set outside R min and inside R max In this embodiment, the candidate region R is set in the region of R max .

[0081] When the determination of the candidate region is completed in S1301, the host device HC1 proceeds to S1302 and divides the candidate region R into a grid pattern. Fig. 14(c) shows the state where the candidate region R is divided into a grid pattern. The size of each grid should satisfy a size that includes the size of the created code, and it is desirable to make the size as small as possible in order to increase the number of candidate regions within it. Let the width of each grid in the Y direction be c and the width in the X direction be d. It is desirable to set the width c in the Y direction to be larger than the width of 20 mm in the Y direction of the code generated in S1104, and the width d in the X direction to be larger than the width of 10 mm in the X direction of the code. The embedding position of the code for each page is selected from the grids divided above.

[0082] The code for each page embedded at the selected grid position will be recorded without extending beyond the grid. Furthermore, the code for each page can be recorded at mutually opposing positions in both the X and Y directions. This makes this embodiment effective in cases where there is a defect somewhere in the nozzle that may occur in the Y direction, or where there are scratches or dirt on the intermediate transfer body that may occur in the X direction. Even if defects continue to occur at fixed positions on the recording medium P, recording the code at mutually opposing positions on each page reduces the possibility of being affected by defects at fixed positions. In the above example, the grid was divided to be larger than the size of the code, but the division unit of the candidate region R is not limited to this. For example, the width c in the nozzle row direction of the divided grid unit may be divided to be greater than or equal to the Y-direction size of the multiple ejection substrates 301, 302, 303, and 304 of the recording head 30 as described in Figure 8. If a different grid is selected in the Y direction, the code for each page embedded at the selected grid position will not be recorded on the same ejection substrate but on different ejection substrates. This reduces the impact on the codes recorded on each page, even if ejection defects continue to occur at the fixed position of the ejection substrate. Next, in S1303, the host device HC1 performs a narrowing process to determine the position in which to embed the codes from among the divided grid.

[0083] Figure 15 is a detailed flowchart of the process in S1303 of Figure 13. When the host device HC1 starts the grid narrowing process, it acquires the image region in S1501. The range of the image region differs for each page, and here the positional information of images 11, 12, 13, and 14, as shown in Figure 14(c), is acquired. For example, one method is to acquire the coordinates of the top left (X1, Y1) and the bottom right (X2, Y2) for each of images 11, 12, 13, and 14 to determine the rectangular region of the image.

[0084] In S1502, the host device HC1 removes grids containing image regions from the candidate region R. Region S1, indicated by a thick border in Figure 14(d), is a set of grids within the candidate region R that contain at least a portion of the image regions of images 11, 12, 13, and 14. If a code is embedded in the grids within this region S1, the image and the code will overlap. As explained above, in this embodiment, overlapping images and codes can cause errors during inspection, so it is desirable to remove region S1 from the candidate region R.

[0085] In S1503, the host device HC1 acquires the defective area from the inspection unit 138. An example of how to acquire the defective area is described below. Each of the grids divided in S1302 is provided with a grid ID that is identifiable to each other. Recording defects detected by the inspection unit 138 are stored in the storage unit 132 for each recording object P'. Furthermore, if the inspection unit 138 detects consecutive defects with the same grid ID for each recording object P', it is determined to be a position-dependent defect. In this embodiment, as shown in Figure 14(d), the area S2 containing defects D that occur consecutively in the upper left area is stored as the grid ID. Note that the acquisition of the defective area is not limited to acquisition from the inspection unit 138; it may also be acquired using information from sensors that detect ejection abnormalities in the recording head.

[0086] In S1504, the host device HC1 removes region S2 from the candidate region R. It is desirable to remove region S2 from the candidate region R because embedding a code in the grid within region S2 would result in the code overlapping with defect D. In S1505, the host device HC1 obtains region or grid IDs that have already been embedded on other pages. Here, since m=1, i.e., it is the first page of processing, there are no regions that have already been embedded. Therefore, the explanation is omitted. S1505 and S1506 will be described later in the example of processing from the second page onwards.

[0087] In S1507, the host device HC1 removes grids smaller than the code size from the candidate region R. Although the grids are basically divided into sections larger than the code size in S1302, the candidate region R is not always divisible by the code size, so there are grids smaller than the code size. Region S3, indicated by the thick border in Figure 14(d), is a set of grids whose length in the Y direction is smaller than the code. Therefore, region S3 is removed from the candidate region R. At this point, the candidate region R has had regions S1, S2, and S3 removed, and the remaining set of grids is updated as the candidate region R. When S1507 is completed, the host device HC1 terminates the grid narrowing process.

[0088] Returning to the explanation of Figure 13, in S1304, the host device HC1 selects one grid from the candidate region R narrowed down in S1303. The method of selection is not particularly limited, but for example, each grid in the candidate region R could be assigned a number, and the grid with the randomly selected number could be chosen. Region C1, indicated by a thick border in Figure 14(d), represents the grid selected here and signifies the region where the code will be embedded in the data D1 on the first page.

[0089] In S1305, the coordinates of region C1 are stored. The rectangular region of the image is saved by storing the coordinates of the top-left (X1, Y1) and bottom-right (X2, Y2) of region C1. Once the processing in S1305 is complete, the host device HC1 terminates the process of determining the code embedding position.

[0090] Next, we will explain the detailed processing in S1105 when m=2, i.e., the second page, in the flow chart of Figure 11. In the following explanation, we will basically proceed with the processing shown in Figures 13 and 15 in the same way as when m=1 page. Note that explanations will be omitted where appropriate for parts where the processing is the same as on the first page.

[0091] Figure 16 illustrates the state of candidate regions at each step of the code embedding position determination flow in Figure 13. It describes the case of determining the position for data D2 on the second page of Figure 12. In S1301, the host device HC1 sets the candidate region R for the code embedding position. Figure 16(a) shows the candidate region R set on the second page. Similar to the first page, the recordable area Rmax specific to the recording device is set as the candidate region R. In S1302, the host device HC1 divides the candidate region R into a grid. Figure 16(b) shows the divided state of the candidate region R on the second page. The size of the code to be embedded is the same as on the first page, and the division size of the candidate region R is also the same as on the first page.

[0092] In S1303, the divided grid is narrowed down. Figure 16(c) is a diagram illustrating the regions that are omitted after the narrowing down process in Figure 15, similar to the first page. The regions that are omitted are the set of grids S1 containing the image region 21, the set of grids S2 containing the defect region D, and the set of grids S3 smaller than the code. Furthermore, in S1506, region C2 is omitted from the candidate region R. Region C2 is the same as region C1 on the first page where the code was embedded. At this point, the candidate region R on the second page has regions S1, S2, S3, and C2 omitted, and is updated as the region with white grids remaining, as shown in Figure 16(c). By repeating the above process for M pages, data is generated in which the codes to be embedded on each page are recorded in different positions.

[0093] Next, we will explain the analysis of the recorded code in the code analysis unit 1002. Figure 22 shows the flow of the analysis performed in the code analysis unit 1002. In the description of each process, the symbol "S" indicates a step in that flowchart.

[0094] When the code analysis unit 1002 starts analyzing the code, it obtains the coordinates of the code embedding region C in S2201. The coordinates may be sent to the storage unit 132 when the code embedding region C is determined in S1304, and then retrieved from the storage unit 132 during code analysis. Alternatively, the coordinates of region C may be obtained using existing pattern matching.

[0095] In S2202, the code analysis unit 1002 performs image processing on the code embedding region C. Here, the image processing range is narrowed from the entire inspection image input by the inspection image input unit 1001 to the code embedding region C, and image processing is performed. At that time, other image processing may or may not be performed on the area of ​​the inspection image excluding the code embedding region C. In either case, image processing suitable for code recognition is performed on the code embedding region C. An example of image processing suitable for code recognition is described below.

[0096] Depending on the ink color or the recording density of the code, the ratio of the combined values ​​of each (R, G, B) channel of the reading may be changed, or a single-channel image may be created by using only specific channels depending on the ink color. When using only specific channels depending on the ink color, it is best to use the channels corresponding to the wavelengths absorbed by the ink color. For example, areas where cyan ink is recorded absorb the red wavelength range (approximately 600 nm), so they are imaged as black in the R channel. On the other hand, areas where cyan ink is not recorded reflect the red wavelength range (approximately 600 nm), so they are imaged as white in the R channel. This allows for high contrast between areas recorded with cyan ink and areas where it is not recorded.

[0097] Similarly, high contrast can be obtained by using the G channel for areas recorded with magenta ink and the B channel for areas recorded with yellow ink. Alternatively, a threshold can be set on the signal value to convert it to a binary grayscale image, or contrast can be improved using a pixel value conversion table with hysteresis characteristics. Other existing contrast enhancement techniques can also be used. Furthermore, these can be combined and implemented. In Figure 22, image processing was performed on the code embedding region C of the inspection image input to the inspection image input unit 1001, but the inspection unit 9A may output a high-contrast image after performing the thresholding or conversion with hysteresis characteristics as described above.

[0098] In S2203, the code analysis unit 1002 performs code analysis. The code analysis is performed using a predetermined existing technology according to the code standard. Then, it obtains information represented by numbers or letters embedded in the code. When the processing in S2203 is completed, the code analysis unit 1002 terminates this flow. Through the analysis in this flow, the original source data that corresponds to the inspection image is identified, and a comparison inspection is performed between the inspection image and the original source data.

[0099] As explained above, this embodiment reduces the possibility of the defective portion and the code overlapping. Specifically, in this embodiment, where the recording head 30 is a full line head, even if a defect occurs at a fixed position due to a malfunction of a nozzle, the possibility of the code and the defect continuing to overlap is reduced, improving the likelihood of being able to perform the inspection normally. Another possible method is to embed multiple codes representing the same information on each page so that if one code overlaps with a defect at a fixed position, another code will be used for reading. However, this method would require a large area on the image data and recording medium for recording the codes, and this embodiment is superior when considering cases where there is insufficient margin or when it is not possible to record overlaid on the image.

[0100] <<Embodiment 2>> Embodiment 1 describes a method for embedding inspection codes at different locations on each page of the original data. However, the locations where the codes are embedded do not need to be different on all pages. The reason for this is as follows: As described in the description of the transfer unit, the transfer body 2 is provided on the outer surface of the transfer drum 41. When the transfer drum 41 completes one rotation, original data for a number of pages that can be transferred to multiple recording media P are formed as ink images IM on the transfer body 2. For example, when the transfer drum 41 completes one rotation, ink images IM for four pages of original data, corresponding to four recording media P, are formed on the transfer body 2. In this case, if a defect such as a scratch or foreign matter adherence occurs in a certain area on the transfer body 2, an image defect will occur in the same area regularly on one in four recordings P'. That is, if a defect that occurs in a certain area on the transfer body 2 occurs as an image defect on the first recording P', then image defects will occur in the same area on the 5th, 9th, 13th, and so on of recording P'. Furthermore, pages 2-4, 6-8, 10-12, etc., are not affected by defects on the transfer medium 2. In this embodiment, we will explain a method for determining the position to embed the code on each page, assuming such a case.

[0101] Figure 17 illustrates the flow of the document data generation process performed in the host device HC1 in this embodiment. This flow is realized by the CPU expanding the program stored in the program memory of the host device HC1 into the data memory and executing it. In the description of each process, the symbol "S" indicates a step in that flowchart.

[0102] When the host device HC1 starts the document data generation process flow, it generates imposition data for the images to be recorded in S1701.

[0103] Figure 18 shows an example of imposition data generated in this embodiment. On the first page, data D1 has only image 11 imposed in the center. On the second page, image 21 is imposed in the same area, and on the third page, data 31 is imposed in the same area, and so on, with all pages up to the last page, page 15, being imposed with the same layout. Thus, this embodiment can be applied to recordings P in which all pages, or pages at regular intervals, are imposed with the same layout. Furthermore, even if the imposition layout differs on all pages, this embodiment can be applied if a non-image area is common to each page. Here, the vertical and horizontal sizes of data D1, D2, D3...D15 are assumed to be the size of the recording medium P loaded on the feeding unit 7. In S1702, the host device HC1 obtains the number of pages M of the imposition data. In this embodiment, as shown in Figure 18, M = 15.

[0104] In S1703, a predetermined number of consecutive pages L is set. This is the number of pages on which the code is embedded in the same position consecutively, and it sets the number of recordings P' that are transferred when the transfer drum 41 completes one rotation. In this embodiment, as described above, four recordings P' are recorded when the transfer drum 41 completes one rotation, so L is set to 4.

[0105] In S1704, the host device HC1 starts the process of embedding a verification code into the data D1 on the first page, with m=1 being the number of pages to be processed. In S1705, it starts processing with l=1 being the number of consecutive pages to which the code will be embedded in the same position. In S1706, the embedding position of the code is determined. The method for determining the embedding position of the code can be determined using the flows in Figures 13 and 15 described in Embodiment 1.

[0106] In S1707, the host device HC1 generates an inspection code to be embedded on the first page. The information that forms the basis of the generated code is the identification value of data D1 on the first page. Similar to the method described in Embodiment 1, the code is generated from a single identification value for the data in its imposed state. In this embodiment as well, the identification value of data D1 on the first page is "000001". The method for converting "000001", the identification value of data D1 on the first page, into a code is the NW-7 standard described in Embodiment 1. Furthermore, it is desirable that the generated code size be the size recommended by each standard, similar to Embodiment 1.

[0107] In S1708, the host device HC1 embeds the code generated in S1707 into data D1 on page m=1. Here, the position where the code is embedded is the coordinate determined in S1706.

[0108] In S1709, the host device HC1 sets m=m+1 and starts the process of embedding the test code on the second page. In S1710, the host device HC1 sets l=l+1 and counts the number of consecutive pages on which the code is embedded in the same position as the second page. In S1711, it is determined whether the processing for 15 pages, which is the number of pages already acquired, has been completed. Since this is the step where the processing for the second page has started, it is determined that the processing for 15 pages has not been completed and the process proceeds to S1712.

[0109] In S1712, the host device HC1 determines whether processing of the set number of consecutive pages, which is 4 pages, has been completed. Since processing of the 2nd page has just begun, it determines that processing of 4 pages has not been completed and returns to S1707 to generate the code to be embedded in the 2nd page. The code to be embedded in the 2nd page is generated from the identification value "000002" of data D2 on the 2nd page in Figure 12. Then, in S1708, the host device HC1 embeds the code generated in S1707 into data D2 on m=2 pages. Here, the position where the code is embedded is the same coordinate as on m=1 page, which was determined in S1706. In this way, the code is synthesized in the same area consecutively up to the pre-set L=4 pages. When processing up to m=4, i.e., the 4th page, is completed, l=1 is set in S1705 and the number of consecutive pages is reset. If m=5, in S1706 the host device HC1 determines a new embedding position to be used for pages 5 to 8. Similarly, the process of embedding the code in each page of the original data is repeated up to m=15.

[0110] In S1711, the host device HC1 determines that processing is complete for all acquired pages and terminates this flow. Through this process, one code can be embedded in each of the 15 pages of the imposition data.

[0111] By performing the above process, the code is embedded in the same position for every set number of consecutive pages L. In this embodiment, L=4 is set, so the code is embedded in the same position on the first to fourth pages of the recording material P'. Then, the embedding position changes on the fifth page, and the code is embedded in the same position on the fifth to eighth pages. If a defect in a certain area on the transfer material 2 affects the first, fifth, ninth, and thirteenth pages of the recording material P', the possibility of the code and the defect continuing to overlap is reduced, thereby improving the likelihood of being able to perform the inspection correctly.

[0112] <<Embodiment 3>> Embodiment 1 describes a method for embedding inspection codes at different locations on each page of the original document data. Embodiment 2 describes a method for embedding inspection codes at different locations at predetermined intervals of a certain number of pages of the original document data. This embodiment describes a case where the embedding at the same location is repeated on pages at predetermined intervals. For example, this embodiment is effective when the range of the candidate area R to which the code is to be embedded is small.

[0113] Figure 19 is a diagram illustrating the flow of the document data generation process performed by the host device HC1 in this embodiment. This flow is realized by the CPU loading the program stored in the program memory of the host device HC1 into the data memory and executing it. The symbol "S" in the description of each process indicates a step in that flowchart. When the host device HC1 starts the document data generation process flow, at S1901 it generates the imposition data for the images to be recorded.

[0114] Figure 20 shows an example of imposition data generated in this embodiment. On the first page, data D1 contains only image 11. The size of image 11 is assumed to be slightly smaller than the recordable area of ​​the recording medium P. On the second page, image 21 is imposed in the same area, and on the third page, data 31 is imposed in the same area, and this same imposition is maintained until the last page, page 15. Here, the vertical and horizontal dimensions of data D1, D2, D3...D15 are assumed to be the size of the recording medium P loaded in the feeding unit 7.

[0115] In S1902, the host device HC1 obtains the total number of pages M of the imposition data. In this embodiment, M is set to 15 as shown in Figure 20. In S1903, the host device HC1 sets a predetermined periodic page number L. This is the number of pages on which codes are embedded in consecutively different positions. Codes are embedded in different positions from page 1 to page L, but from page L+1 onwards, the embedding position returns to that of page 1 and is embedded again. In this embodiment, L is set to 7. The setting method will be described later.

[0116] In S1904, the host device HC1 sets the page to be processed as m = 1 and starts the process of embedding the inspection code into the data D1 on the first page. In S1905, the host device HC1 starts the process with l = 1, which is the number of pages for continuously embedding the code at different positions. In S1906, the host device HC1 determines the embedding position of the code. The method for determining the embedding position of the code will be described in detail later.

[0117] In S1907, the host device HC1 generates the code using the same method as in Embodiment 1 and Embodiment 2. In S1908, the host device HC1 embeds the code generated in S1907 into the data D1 on the first page, that is, m = 1. Here, the position for embedding the code is the coordinate determined in S1906. In S1909, the host device HC1 sets m = m + 1 and starts the process of embedding the inspection code into the second page. In S1910, the host device HC1 sets l = l + 1 and counts the number of pages for continuously embedding the code at different positions as the second page.

[0118] In S1911, while m < L + 1, the host device HC1 repeats S1906 to S1910 and continues the process of embedding the code at a new position. In this embodiment, the predetermined periodic page number L = 7, so the code is embedded at different positions up to the seventh page. At the eighth page, it proceeds to S1912.

[0119] In S1912, the host device HC1 determines whether processing for the 15 pages already acquired has been completed. Here, processing for up to page 8 has been completed, but processing for page 15 has not been completed, so the device proceeds to S1913. In S1913, the host device HC1 determines whether the number of pages in which codes are embedded in consecutively different positions exceeds a predetermined cycle page number L. Here, l=8, and it determines that it exceeds the predetermined cycle page number L=7, so the device proceeds to S1914. In S1914, the host device HC1 resets the number of pages in which codes are embedded in consecutively different positions to l=1.

[0120] In S1915, the host device HC1 obtains the code embedding position for the case l=1, which was stored in S1906. In S1907, the host device HC1 generates the code for m=8, i.e., the 8th page. In S1908, the host device HC1 embeds the code generated in S1907 into data D8 on the 8th page. Since the value of l was reset in S1914, the embedding position becomes l=1, i.e., the same coordinates as the 1st page. In S1909, the host device HC1 sets m=m+1 and starts the process of embedding the verification code on the 9th page. In S1910, the host device HC1 sets l=l+1 and counts the number of pages in which codes are embedded in consecutively different positions as the 2nd page. In S1911, the host device HC1 proceeds to S1912 because m=9, i.e., the number of pages to be processed is greater than the predetermined periodic page number L=7. In S1913, the host device HC1 proceeds to S1913 because m=9, i.e., the number of pages to be processed has not reached the page count M=15. In S1913, the host device HC1 proceeds to S1915 because l=2, i.e., the number of pages on which codes are to be embedded in consecutively different positions is less than the predetermined cycle page count. In S1915, the host device HC1 retrieves the code embedding positions for l=2 that were stored in S1906. From page 8 to page 14, in S1915, the code embedding positions for pages 1 to 7 are retrieved, and the code is embedded in the same positions for each page. That is, in this flow, the code will be embedded in the same position on page 8 as on page 1, and in the same position on page 9 as on page 2, and so on. The process of embedding codes in each page of the manuscript data is repeated in the same way until m=15. In S1912, the host device HC1 determines that processing is complete for all retrieved pages and terminates this flow. With the processing described so far, we can embed one code into each of the 15 pages of the imposition data.

[0121] Figure 21 illustrates the state of candidate region R at each step in Figure 13, which shows the detailed flow of S1906. It explains the case of determining the position for data D1 on the first page of Figure 20.

[0122] In S1301, the candidate region R for the code embedding location is set. Figure 21(a) shows the case where the candidate region R is at its maximum. max This is an example. As explained in Embodiment 1, R max This is an area where a code can be recorded, and in this embodiment, the candidate area R is also R max The region is set. In S1302, the host device HC1 divides the candidate region R into a grid.

[0123] Figure 21(b) shows the candidate region R divided into a grid. The division size can be determined as appropriate, as in Embodiment 2. In S1303, the host device HC1 performs a narrowing process of the divided grid. The narrowing is performed using the flow shown in Figure 15, as in Embodiments 1 and 2. As explained in Embodiment 1, the set of grids S1 that includes at least part of the image region, the set of grids S2 that includes at least part of the defect region D, and the set of grids S3 whose vertical and horizontal sizes are fractional are excluded from the candidate region R.

[0124] Figure 21(c) is an explanatory diagram of the state after the narrowing down process. S1, S2, and S3 are omitted, and the remaining area is updated as m=1, i.e., candidate embedding location R for the first page. As a result of the above processing, in this embodiment, as shown in Figure 21(c), there are only 7 candidate embedding locations for the code on the first page, i.e., based on the number of grid cells. Since M=15, 15 codes must be embedded for these 7 candidates. Therefore, in this step for the first page, it is desirable to provide feedback to S1903 as described above and set L=7. The value of the periodic page number L should be set to the same value as the number of candidate areas R, or to a value smaller than the number of candidate areas R.

[0125] In S1304, the host device HC1 selects one grid from the candidate region R narrowed down in S1303. The selected area is designated as the code embedding region C. There are no particular restrictions on the selection method, but for example, each grid in the candidate region R could be assigned a number, and the grid with the randomly selected number could be chosen. Region C1, indicated by a thick border in Figure 21(c), represents the grid selected here and signifies the area where the code will be embedded in the data D1 on the first page.

[0126] In S1305, the host device HC1 stores the coordinates of region C1. The rectangular region of the image is saved by storing the coordinates of the top-left (X1, Y1) and bottom-right (X2, Y2) of region C1. The coordinates are accumulated and recorded for each l as the count of l ranges from 1 to L. In S1306, the host device HC1 finishes the process of determining the code embedding position. By performing the above process, the seven embedding candidate regions R, shown as white areas in Figure 21(c), are selected one by one from page 1 to page 7, and the code is embedded. From page 8 onwards, the code is embedded again in the regions that were embedded on page 1.

[0127] As explained above, according to this embodiment, even when the number of grid cells in the candidate region R for code embedding is small, the code will be embedded in relatively different locations. This reduces the possibility of the code continuing to overlap with defects, thereby improving the likelihood of successful inspection.

[0128] <<Other Embodiments>> In Embodiment 1, the explanation was given using the imposition data shown in Figure 12; in Embodiment 2, in Figure 18; and in Embodiment 3, in Figure 20. When embedding codes into this imposition data, an example was given in which one code is embedded on each page, but the effect is not limited to this. That is, even when embedding multiple codes on a single page, the same effect can be obtained as long as the embedding positions of the multiple codes on each page do not coincide across pages. When embedding multiple codes on a single page, some of the codes may represent the same information.

[0129] In each embodiment, the set of grids S1 containing the image region was excluded from the candidate region R, but this is not limited to this. For example, in S1502, non-image regions may be excluded from the candidate region R. In that case, the candidate region R will consist only of image regions, and the code embedding position will be determined at a position overlapping with the image. A method for embedding a code at a position overlapping with an image may be to use a digital watermarking technique by multiplexing, such as the one described in Japanese Patent Application Publication No. 2019-009733. Digital watermarking by multiplexing is a technique for embedding additional information other than the image into an image on a recording in a way that is not visually discernible. By using this, it is possible to embed a code in the image region as well by embedding an inspection code that is not visually discernible into the image. When embedding a code by multiplexing, the original data used as the comparison source during inspection may be the data after the code has been embedded, or it may be the data before the code has been embedded. To improve the accuracy of the inspection, it is desirable to use the original data before the code has been embedded in order to prevent errors caused by multiplexing. Furthermore, even when using manuscript data with embedded codes, it is possible to prevent errors by excluding the pre-duplicated portions from the inspection target.

[0130] Furthermore, in Figure 15, which illustrates the process of narrowing down the candidate region R for the code embedding position, the image region, known defect region, and embedded region are excluded from the candidate position R. In addition to these, the region where various check patterns for checking recording performance are recorded may also be excluded. Here, the various check patterns refer to check patterns for adjusting the relative recording positions of multiple ink colors used for recording. However, they are not limited to these; they may also be nozzle check patterns for confirming whether ink is being ejected normally from the nozzles of the recording head 30. Other examples include color monitor patterns for confirming the hue or density of the recording region corresponding to each nozzle of the recording head 30.

[0131] Furthermore, if the areas where the various check patterns described above are recorded are not omitted, the code embedding position may be determined to overlap with the check patterns. When embedding a code in a position that overlaps with a check pattern, it is desirable to generate the data in such a way that the code is recorded preferentially over the check pattern in that embedding area. This is because, since the various check patterns are recorded on every page, under the conditions of each embodiment where the code embedding position is not fixed, there will be an opportunity for the check pattern to be recorded in that area on at least one page. On the other hand, since the code for inspection needs to be linked to the manuscript data on a page-by-page basis, it is impossible to supplement it on other pages. Therefore, if the code embedding position is determined to overlap with the various check patterns, it is desirable to prioritize the recording of the code.

[0132] In each embodiment, the ink used in the explanation is assumed to contain a colorant. However, the components of the ink are not limited to this, and invisible ink may be used, for example. Invisible ink is an ink that is not recognizable as a color under visible light such as sunlight, but has the property of fluorescing in the visible light range when irradiated with a specific wavelength such as ultraviolet light. Here, we will explain using invisible ink that emits light when irradiated with ultraviolet light.

[0133] In Embodiments 1, 2, and 3, the type of ink used to record the code is simply replaced with invisible ink, and inspection becomes possible by irradiating the code recording area with ultraviolet light when reading the code, thus achieving the same effect.

[0134] Furthermore, consider steps S1501 and S1502 in Figure 15, which explain the process of narrowing down the candidate region R for the code embedding location. In each embodiment, the set of grids S1 containing the image region was excluded from the candidate region R, but this step may be skipped when recording the code with invisible ink. That is, the code embedding location can be in either the image region or the non-image region. In this case as well, inspection is possible by irradiating the code recording area with ultraviolet light when reading the code, and the same effect can be obtained.

[0135] Furthermore, even when using invisible ink for code recording, non-image areas may be excluded from the candidate area R. In this case, the code will only be recorded in the image area, but the same effect can be obtained. As described above, even when using invisible ink for code recording, the same effect can be obtained as long as the recording positions of multiple codes are different.

[0136] While each embodiment assumed a sheet-fed recording system, the effects are not limited to this. The effect is effective as long as the position of the code embedded on each page of the imposition data is not fixed, so the recording medium actually used may be roll paper.

[0137] Furthermore, in the above embodiment, the recording unit 3 is equipped with a line head that performs full multi-track recording on a sheet-fed recording medium or a web-type recording medium, but it may also have a single recording head 30. That is, the recording head 30 does not have to be a full line head, and it may be a serial method in which ink is ejected from the recording head 30 while a carriage on which the recording head 30 is detachably mounted is moved relative to the recording device in the Y direction, thereby forming an ink image. Even when performing serial recording, a malfunction in one of the following components may cause a defect in the fixed position corresponding to the location of the malfunction. For example, these include the transport rollers that transport the recording medium P, the discharge rollers, the spurs that follow them and rotate in contact with the recording medium P, the platen that supports the back surface of the recording medium P, or the guide rails for scanning the carriage on which the recording head is mounted.

[0138] The transport mechanism for the recording medium P may be any other method, such as a method in which the recording medium P is held and transported by a pair of rollers. In the method of transporting the recording medium P by a pair of rollers, a roll sheet may be used as the recording medium P, and the roll sheet may be cut after transfer to produce the recorded material P'. In each of the above embodiments, the transfer body 2 is provided on the outer surface of the transfer drum 41, but other methods may be used, such as a method in which the transfer body 2 is formed in an endless strip shape and travels in a cyclic manner.

[0139] In each embodiment, the generation of the inspection code was performed by the recording data generation unit 202 of the host device HC1, which is an information processing device. However, by receiving the original data from the host device HC1 or another device, the code can also be generated by the main controller 13A of the recording device 1A.

[0140] Furthermore, the present invention can also be realized by supplying a program that implements one or more of the functions of the above embodiments 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 realized by a circuit (e.g., an ASIC) that implements one or more functions.

Claims

1. A code generation means that generates a code for identifying each image in imposition image data in which one or more images are impositioned on a recording area, Candidate area determination means for determining candidate areas for placing the code in the recording area such that the code is not recorded in the same position in the recording area of ​​each page of multiple imposition image data, Recording data generation means for generating recording data based on imposition image data such that the code is placed in at least one of the candidate regions determined by the candidate region determination means, Output means for outputting the generated recording data to a recording device, Equipped with, The candidate region determination means is an information processing device characterized by excluding from the candidate regions regions regions regions that have been determined to be defective regions by a sensor that checks the recording status, which is obtained from the recording device.

2. The information processing apparatus according to claim 1, characterized in that the recording data generation means generates the recording data such that the recording position of the code differs between the first page, which is a predetermined page of the imposition image data, and the second page that follows the first page.

3. The information processing apparatus according to claim 1, characterized in that the recording data generation means generates the recording data such that the recording position of the code is the same on the first page and on the second page following the first page up to a predetermined number of pages of the imposed image data, and is at a different position on the first page and on the second page at the predetermined number of pages of the imposed image data.

4. The information processing apparatus according to claim 1, wherein the recording data generation means generates recording data such that the recording position of the code differs between the first page and the second page following the first page in a predetermined number of pages of the imposition image data.

5. The information processing apparatus according to claim 4, characterized in that the code is recorded at the same position on the first page of the predetermined cycle and on the first page of the next cycle.

6. The information processing apparatus according to claim 4 or 5, characterized in that the number of candidate regions is at least the number of pages in a predetermined period.

7. The information processing apparatus according to any one of claims 2 to 4, characterized in that when the recording data generation means generates a code at different positions on the first page and the second page, it generates the recording data such that at least one of the positions on the imposition image data is different in the X direction, which represents the transport direction, or in the Y direction, which represents a direction perpendicular to the X direction.

8. The information processing apparatus according to any one of claims 1 to 7, characterized in that the candidate region determination means excludes an image placement region in which an image is placed in the imposition image data from the candidate region.

9. The information processing apparatus according to any one of claims 1 to 8, characterized in that the candidate region determination means excludes from the candidate region a region in which various check patterns for checking recording performance are recorded.

10. The information processing apparatus according to claim 9, characterized in that the recording data generation means generates recording data such that, if the area where the various check patterns are recorded overlaps with the recording position of the code, the code is given priority in recording.

11. The information processing apparatus according to claim 9 or 10, characterized in that the various check patterns are check patterns for adjusting the relative recording positions of multiple ink colors used for recording, nozzle check patterns for confirming whether ink is being ejected normally from the nozzles of the recording head, or color monitor patterns for confirming the hue or density of the recording area corresponding to each nozzle of the recording head.

12. The information processing apparatus according to any one of claims 1 to 11, characterized in that the recording data generation means generates recording data such that the code is recorded using invisible ink in the area where the image is arranged.

13. The information processing apparatus according to any one of claims 1 to 12, characterized in that the recording data generation means generates recording data using visible ink and multiplexing so that the code is recorded.

14. The recording device performs recording using a transfer method with intermediate transfer bodies intermittently attached to the surface of a transfer drum, and the predetermined number of pages of the imposition image data is the number of intermediate transfer bodies, as described in claim 3.

15. The information processing apparatus according to claim 14, characterized in that the recording device comprises a line head that performs full multi-track recording on a single-fed recording medium or a web-like recording medium.

16. The information processing apparatus according to claim 14, characterized in that the recording device comprises a line head that performs serial recording, moving relative to a sheet-fed recording medium or a web-like recording medium.

17. The information processing apparatus according to claim 15 or 16, characterized in that the candidate region is a grid unit divided by a length greater than or equal to the size of the discharge substrate constituting the line head.

18. The information processing apparatus according to any one of claims 1 to 16, characterized in that the candidate region is a grid unit divided by a length greater than or equal to the size of the code.

19. The information processing apparatus according to claim 1, characterized in that the recording data generation means arranges a plurality of codes within the pages of the imposed image data.

20. A code generation step that generates a code for identifying each image in imposition image data in which one or more images are impositioned on a recording area, A candidate area determination step in which candidate areas for placing the code in the recording area are determined such that the code is not recorded in the same position in the recording area of ​​each page of multiple imposition image data, A recording data generation step that generates recording data based on the imposition image data such that the code is placed in at least one of the candidate regions determined in the candidate region determination step, An output step of outputting the generated recording data to a recording device, Equipped with, The candidate region determination step is a control method for an information processing device characterized by excluding from the candidate regions regions regions regions that have been determined to be defective regions by a sensor that checks the recording status, which is obtained from the recording device.

21. A program for causing a computer to function as one of the means of an information processing apparatus described in any one of claims 1 to 19.

22. A recording system including an information processing device and a recording device, The aforementioned information processing device is A code generation means that generates a code for identifying each image in imposition image data in which one or more images are impositioned on a recording area, Candidate area determination means for determining candidate areas for placing the code in the recording area such that the code is not recorded in the same position in the recording area of ​​each page of multiple imposition image data, Recording data generation means for generating recording data based on imposition image data such that the code is placed in at least one of the candidate regions determined by the candidate region determination means, The system includes output means for outputting the generated recording data to a recording device, The candidate region determination means determines the candidate regions by excluding regions that have been determined to be defective regions by a sensor that checks the recording status, which is obtained from the recording device. The recording device is Recording means for recording based on the aforementioned recorded data, An inspection means that reads a recorded document and performs an inspection using the code, A recording system characterized by comprising the following features.

Images