DETERMINING A MODULE SIZE OF AN OPTICAL CODE

Abstract

A method for determining a module size of an optical code (20), wherein image data with the code (20) are detected, a brightness distribution is determined from the image data, and the module size is determined from the brightness distribution. The brightness distribution for example is a greyscale histogram.

Claims

1. A method for determining a module size of an optical code (20), wherein image data with the code (20) are detected, a brightness distribution is determined from the image data, and the module size is determined from the brightness distribution.

2. The method according to claim 1, wherein the brightness distribution is a greyscale histogram.

3. The method according to claim 1, where the module size is determined from a central region of the brightness distribution.

4. The method according to claim 1, wherein edges of the optical code (20) are located in the image data and the brightness distribution is formed only over image data in a neighborhood of edges.

5. The method according to claim 1, where the brightness distribution is tailored to an active area where the distribution exceeds a noise threshold.

6. The method according to claim 1, wherein the module size is determined from at least one of a width, an integral and a maximum value of the brightness distribution.

7. The method according to claim 6, wherein the module size is determined from a quotient of the integral and the width of the brightness distribution.

8. The method according to claim 7, wherein the quotient is mapped to the module size with a scaling function.

9. The method according to claim 8, wherein the quotient is mapped using units of pixels per module.

10. The method according to claim 1, wherein the brightness distribution is rescaled with different weighting factors at a center and at sides of the brightness distribution.

11. The method according to claim 10, wherein the center of the brightness distribution is raised relative to the sides.

12. The method according to claim 1, wherein the brightness distribution is divided into three parts, namely a left side, a center and a right side, and wherein a weight factor for each of the three parts is used for rescaling.

13. The method according to claim 1, wherein the optical code (20) is read after determining the module size.

14. The method according to claim 13, wherein the optical code (20) is at least one of read with a decoding method selected on the basis of the module size and parameterized by the module size.

15. The method according to claim 1, wherein the determined module size is compared with a limit value in order to use a decoding method or a component of a decoding method depending on whether the module size exceeds or falls below the limit value.

16. The method according to claim 15, wherein the limit value is in a range of a module size of one to three pixels per module.

17. A code reader (10) for reading optical codes (20), comprising an image sensor (24) for detecting image data with the code (20) and a control and evaluation unit (26) configured to read the code (20) after determining a module size of the code (20), the module size being determined from a brightness distribution that is determined from the image data.

18. The code reader (10) according to claim 17, wherein the brightness distribution is a greyscale histogram.

Description

[0030] The invention will be explained in more detail in the following also with respect to further features and advantages by way of example with reference to embodiments and to the enclosed drawing. The Figures of the drawing show in:

[0031] FIG. 1 a schematic three-dimensional overview of the exemplary installation of a code reader above a conveyor belt where objects with codes to be read are conveyed;

[0032] FIG. 2 an example of a greyscale profile;

[0033] FIG. 3 a representation of the derivative of the greyscale profile according to FIG. 2 for locating edges;

[0034] FIG. 4 an example of a greyscale histogram of a code with large module size;

[0035] FIG. 5 an example of a greyscale histogram of a code with small module size;

[0036] FIG. 6 a representation of the active area of a greyscale histogram above a noise threshold, illustrating the integral and width of the active area;

[0037] FIG. 7 a flowchart for an exemplary algorithm for determining the module size from a greyscale histogram; and

[0038] FIG. 8a-e exemplary representations of greyscale histograms for different module sizes.

[0039] FIG. 1 shows an optoelectronic code reader 10 in a preferred application situation mounted above a conveyor belt 12 that conveys objects 14, as indicated by the arrow 16, through the detection area 18 of the code reader 10. The objects 14 have code areas 20 on their outer surfaces that are detected and evaluated by the code reader 10. The code areas 20 can only be detected by the code reader 10 if they are arranged on the top or at least visible from above. For this reason, in deviation from the illustration in FIG. 1, a number of code readers 10 can be mounted from different directions to read a code 22 that is arranged at a side or bottom, in order to enable so-called omni-reading from all directions. A plurality of code readers 10 in practice are preferably arranged as a reading tunnel. The stationary application of the code reader 10 at a conveyor belt 12 is very common. However, the invention primarily relates to the code reader 10 itself and its implemented method for decoding codes, or more specifically a preprocessing step to that end, and therefore this example is not to be understood in a restrictive manner.

[0040] The code reader 10 uses an image sensor 24 to detect image data of the conveyed objects 14 and the code areas 20, which are further processed by a control and evaluation unit 26 using image evaluation and decoding methods. The specific imaging method is not important for the invention, so that the code reader 10 can be configured according to any known principle. For example, only one line is detected at any one time, either by means of a line-shaped image sensor or a scanning method, where in the latter case a simple light receiver such as a photodiode is sufficient as image sensor 24. An image line can directly be used for an attempt to read the code, or the control and evaluation unit 26 combines the lines detected during the conveyor movement to form the image data. With a matrix-shaped image sensor, a larger area can be captured in one image, where it is also possible to combine images both in the conveying direction and the transverse direction. The plurality of images may be taken one after the other and/or by a plurality of code readers 10 that for example cover the entire width of the conveyor belt 12 only with their combined detection areas 18, each code reader 10 detecting only one tile of the entire image and the tiles being combined by image processing (stitching). It is also conceivable to decode only fragments within individual tiles and then to stitch the code fragments.

[0041] The main task of the code reader 10 is to detect the code areas 20 and to read the codes therein. As a sub-step, preferably as early as possible in the processing chain and prior to the actual code reading, the module size is determined from a brightness distribution or a greyscale histogram of the images of the respective code 20. This is explained in detail below with reference to FIGS. 2 to 8.

[0042] The code reader 10 provides information, such as read codes or image data, via interface 28. It is also conceivable that the control and evaluation unit 26 is not arranged in the code reader 10 itself, i.e. the camera shown in FIG. 1, but is connected as a separate control device to one or more code readers 10. In this case, interface 28 also is used as a connection between internal and external control and evaluation. The control and evaluation functionality can be distributed to internal and external modules in practically any way, while the external modules can also be connected via network or cloud. No further distinction is made in this regard, and the control and evaluation unit 26 is considered as part of the code reader 10, regardless of the actual implementation.

[0043] FIG. 2 shows an example of image data of a code 20 in the form of a greyscale or grey level profile of an image line through the code 20. This kind of greyscale profile forms the initial data obtained by image sensor 24. The example of a greyscale profile is not a real limitation. Optical codes consist of areas in two modalities, often black and white color, sometimes structures or embossing, but in any case the code information can be captured by greyscale images. It does also not matter for the understanding of the invention whether the greyscale profile is detected as a scan of a bar code scanner, an image line of a line-shaped image sensor or a line through a two-dimensional image of the code 20.

[0044] The further specification is based on the example of barcodes, but the method according to the invention for determining the module size is analogous for two-dimensional codes. In the case of a barcode, the greyscale profile should not be captured almost parallel to the bars. If the module size is to be determined in absolute length units, the angle of the greyscale profile with respect to the code must be known. However, the size of interest for decoding is how many pixels represent a module (ppm, pixel per module), in the very same image data that the decoder receives, including a possible skew in the code 20.

[0045] In principle, the desired module size is already represented in FIG. 2. The respective plateaus at high and low grey values correspond to the characters of the code, so that the widths of the plateaus could be measured and the module size could be fitted as the smallest length from which the widths could be reconstructed by this smallest length or multiples thereof. However, the error is too large by far, in particular in view of lots of the plateaus not even being recognizable as plateaus, let alone allowing for reliable measurement of their width.

[0046] FIG. 3 shows the derivative of the greyscale profile according to FIG. 2. The edges of the code, i.e. the transitions between light and dark code elements and vice versa, are the extrema. Instead of the plateaus as in FIG. 2, the distances between adjacent extrema could thus be used to determine the module size, as already discussed in the introduction. The problem is that the edge positions are noisy and even without noise at best allow a determination of the module size with an accuracy of one pixel, but no subpixel accuracy. However, edge positions that are only roughly determined with these limitations can still be useful for the method according to the invention for determining the module size.

[0047] According to the invention, the module size is not determined from greyscale profiles or derivatives thereof, but an indirect approach via a histogram of greyscale values or, more generally, a brightness distribution is used.

[0048] FIG. 4 shows an exemplary greyscale histogram for a barcode that was recorded with a good resolution and a module size of 2.58 ppm. The small inset picture on the top right shows a real image section for illustration. The greyscale histogram is created by arranging the possible greyscale values, in this case 0-255 corresponding to 8-bit image data, as bins on the X axis. For each pixel of the code image data under consideration, the bin corresponding to the grey value of the pixel is incremented by one. The code's quiet zones preferably are not included in the greyscale histogram. As a final step, there can be a normalization by dividing by the total number of contributing pixels, which ensures that the sum of all bins equals one. The greyscale histogram is a discretization of the brightness distribution, and therefore the more general term brightness distribution is also used in this specification.

[0049] For sufficient module size, the greyscale histogram is bimodal with a clear left and right peak for the dark and light code elements, respectively, and a flat area in between.

[0050] FIG. 5 shows another exemplary greyscale histogram now recorded for a barcode that was recorded with a poor resolution and a module size of 0.93 ppm. Again, the small inset picture on the top right shows a real image section for illustration, which gives an idea why reading such a code requires special attention. The greyscale histogram differs significantly from that of a code recorded with a good resolution and a module size of at least 2 ppm. The bimodality increasingly gets lost with decreasing module size. With increasing blurring due to poor resolution, an increasingly strong peak is formed at medium grey values.

[0051] This illustrates the basic idea of the invention: The brightness distribution, which is obtained in particular as a greyscale histogram, allows conclusions to be drawn about the module size. This may be a qualitative statement as to whether the module size is large or small, with the limit in between for example being 2 ppm, but it is also possible to estimate a numerical value for the module size. FIGS. 4 and 5 again show barcodes as examples. The blurring effects caused by too low a resolution, from which the module size is ultimately determined according to the invention, also occur with two-dimensional codes, so that the example of barcodes must not be understood as restricting.

[0052] As explained with reference to FIGS. 4 and 5, the difference between small and large module sizes is reflected in the different characteristics of the peak for medium grey values. The distinguishability of module sizes is therefore increased if the central or transition region of the greyscale histogram is considered.

[0053] It is therefore advantageous if the greyscale histogram is obtained only from pixels that correspond to this transition area. This can be achieved in that the greyscale histogram is not formed from all pixels of an image of a code, but only from pixels in the neighborhood of edges. There at the edges, the blurring effect due to under-sampling or too low resolution can be measured particularly well.

[0054] It has already been explained with reference to FIG. 3 how the edge positions can be estimated, for example from a derivative of a greyscale profile. The greyscale histogram preferably is formed from the pixels at these edge positions and a respective pixel neighborhood. For the purpose of restricting a grey scale histogram to edge neighborhoods it is not important that the edge positions are only accurate to one pixel, since the subpixel range is anyway not considered in the greyscale histogram. Any edge position errors caused by noise effects are also tolerated, as they only lead to a pixel being wrongly included or excluded every now and then. In any case, this is much better than including all pixels indiscriminately.

[0055] An exemplary greyscale histogram based on edge neighborhoods is shown in FIG. 6. It should be noted, however, that although considering a greyscale histogram consisting only of pixels in a neighborhood of edges is particularly advantageous and allows a particularly good accuracy in determining the module size, the module size nevertheless can also be estimated from simple greyscale histograms that take into account all pixels of an image of a code or code area.

[0056] In order to determine a module size from the greyscale histogram based on edge neighborhoods, or alternatively a complete greyscale histogram, the greyscale histogram may be described by characteristic variables. Only an active area of the greyscale histogram preferably is considered to ensure that individual noise events do not affect the evaluation. This includes only those bins that exceed a noise threshold, for example either specified as a minimum number of pixels contributing to the bin or a minimum percentage.

[0057] It turns out that the width, as illustrated by an arrow in FIG. 6, is a very useful characteristic variable. The width is the difference between the largest and smallest grey value occurring in the greyscale histogram. Another characteristic variable useful for calculating the module size is the area or integral of the greyscale histogram, which can be obtained by summing up the bins.

[0058] The area of a normalized histogram of course is one, so the integral only makes a real contribution if the greyscale histogram is not normalized or is normalized before the active area is determined with the noise threshold, or if subareas are rescaled as explained below. Other possible characteristic variables are the height of the main maximum, the number of secondary maxima or the ratio of the height of the main maximum to the height of the first secondary maximum.

[0059] One possible specific calculation for the module size is to form the quotient of integral and width and to map this measured value with a scaling factor to a module size in units of ppm. The scaling factor can for example be obtained by reading codes in a calibration or teach-in process and subsequently determining the module sizes with high accuracy by common means. Then, in reversal of the later calculation, the known module size is compared with the quotient of integral and width to find the required scaling factor.

[0060] FIG. 7 shows a flowchart for an exemplary algorithm for determining the module size from a greyscale histogram. In this algorithm, some specific steps are provided, which are to be understood as advantageous embodiments and do not limit the generality of the specification.

[0061] In a step S1, input data is obtained, i.e. the image data of the code, for example in the form of one or more greyscale profiles, as explained above with reference to FIG. 2.

[0062] In a step S2, the edge positions in the code are determined. The derivative of greyscale profiles can be used to that end, as explained above with reference to FIG. 3. An accuracy of pixels rather than sub pixels as well as possible position errors due to noise are no obstacle for the estimation of the module size.

[0063] In a step S3, the greyscale histogram is initialized by providing bins according to the possible grey values and initializing the respective bin counters with zero.

[0064] In a step S4, the grey values of the pixels at the edge positions as well as in their neighborhood are determined, for example the preceding i and the following j pixels.

[0065] In a step S5, the bins associated with the grey values determined in step S4 are incremented accordingly. Steps S4 and S5 are separated for explanation only. In practice, rather all edge positions and, for each edge position, the pixels in their neighborhood would be considered one after the other, and for each relevant pixel the bin of the corresponding grey value would be incremented. As an alternative to the edge-based greyscale histogram according to steps S2, S4 and S5, a greyscale histogram can also be formed from all pixels of the input data of step S1, in which case the estimation of the module size may become less accurate.

[0066] In a step S6, the greyscale histogram is normalized so that the sum over all bins is one. The normalization factor corresponds to the number of pixels contributing to the greyscale histogram or the sum over the greyscale histogram prior to normalization. The normalization is completely optional and could in particular also be replaced by using the scaling factor F to be introduced in step S10.

[0067] In a step S7, the greyscale histogram is limited to a so-called active area by only considering bins that have a minimum count or frequency of occurrence exceeding a noise threshold. The noise threshold can be a constant or a fraction of the sum of all bins of frequencies of occurrence, for example a per mille value, and eliminates outliers. A width B is calculated as the difference between the largest and smallest bin of the active area.

[0068] A subsequent step S8 is completely optional and is an example of an optional rescaling of the greyscale histogram that can be used to further enhance certain characteristic properties for determining the module size. In this specific example implementation, the active area is divided into three equally sized partial areas. The bins in the left and right part are multiplied by a side weight, the bins in the central part are multiplied by a central weight. Alternatively, a more finely resolved weighting function could be used. Preferably, the rescaling is used for a relative weakening of the side areas and a relative strengthening of the central area, whatever the specific design of the rescaling. This is because, as explained with reference to FIG. 5, the central transition area of grey values is of particular interest for determining the module size, and is thus emphasized still more.

[0069] In a step S9, the bins of the active area are summed up so that an integral or the area A of the active area is determined.

[0070] In a step S10, the quotient of area A and width B is formed. This already is the desired estimation of the module size, but still in the wrong units. Therefore, the module size is calculated as F*A/B, i.e. a scaling factor F is introduced, which scales the measured variables from the greyscale histogram to a module size in units of ppm. The scaling factor F can be empirically determined or taught-in in advance.

[0071] FIGS. 8a-e show examples of grey scale histograms for different module sizes, each limited to the neighborhood of edges as explained with reference to FIG. 6. The respective actual module sizes were reconstructed with only a small error using the method explained with reference to FIG. 7. Specifically, in FIG. 8a the actual module size is 0.8 ppm and the estimated module size is 0.79 ppm, in FIG. 8b the actual module size is 1.0 ppm and the estimated module size is 1.06 ppm, in FIG. 8c the actual module size is 1.2 ppm and the estimated module size is 1.23 ppm, in FIG. 8d the actual module size is 1.4 ppm and the estimated module size is 1.19 ppm, and in FIG. 8e the actual module size is 1.5 ppm and the estimated module size is 1.68 ppm.

[0072] In a data set of more than 700 code images taken from a real application, an average error of 0.15 of the estimated module size could be achieved. The calculations become less accurate for increasing module sizes. A major reason is that the scaling factor F is actually a scaling function that should be attenuated for increasing module sizes, for example of greater than 2 ppm. In principle, a scaling function can be determined empirically or taught-in in the same way as a scaling factor. In practice, however, this is not really necessary, since the small module sizes, where a constant scaling factor F results in a good estimation, are the more critical cases by far, and an estimation error for increasing module sizes can therefore usually be accepted.