McodeRead

See also

User Guide:

2D graphics list Automatically detecting the code type Code context initialization modes Customizing read and grade operation settings Organization of the MIL modules Retrieving results Steps to reading, grading, or writing a code in an image Supported encoding schemes, sub-types, and error correction schemes by code type Training read and grade operation settings Using child buffers, ROIs, or a copy to manipulate specific data areas Verification process and grading your code Working with real-world units

Reference:

MbufInquire MbufSetRegion McodeControl McodeGetResult McodeModel

Availability

Not available in MIL-Lite

Available in MIL

Available on Windows

Available on Linux

Not supported on:

Not supported on Matrox Indio (Update 53 or Update 68) (w)

Not supported on Matrox Concord PoE with ToE (Update 82) (z)

Fully supported on:

Fully supported on Host system (a)

Fully supported on Matrox GigE Vision driver (MIL 10, Update 25, Update 54, or Update 85)* (c)

Fully supported on Matrox Morphis (g)

Fully supported on Matrox Morphis QxT (h)

Fully supported on Matrox Orion HD (i)

Fully supported on Matrox Radient eCL (j)

Fully supported on Matrox Radient eV-CXP (MIL 10 or Update 29)* (k)

Fully supported on Matrox Solios eA/XA (l)

Fully supported on Matrox Solios ecl/xcl/ev-cl (m)

Fully supported on Matrox USB3 Vision driver (Update 19) (o)

Fully supported on Matrox RadientPro-CL (Update 7) (p)

Fully supported on Matrox Radient eV-CL (Update 27 or 74) (r)

Fully supported on Matrox Iris GTR (Update 28 or Update 68) (t)

Fully supported on Matrox Clarity UHD (Update 36 or 76) (u)

Fully supported on Matrox GenTL driver (Update 34) (v)

Fully supported on Matrox Rapixo CXP (Update 75 or Update 84) (y)

Fully supported on Matrox Rapixo CL Pro (Update 96) (aa)

* Refer to the MIL system-specific information
in the MIL Reference for the minimum update required.

For any information regarding a MIL system added during a MIL Update, see the MIL system’s release note

Available on Non-Matrox computer

Available on Matrox 4Sight-X

Available on Matrox 4Sight GP/GPm

Available on Matrox Supersight

Function map

Examples

codedetect.cpp
codegrading.cpp
codetrain.cpp
dotspacing.cpp
fixturedcoderead.cpp
fixturingusingblob.cpp
mcode.cpp
mcode.cs
mcode.vb
multipledatamatrixcoderead.cpp
pharmacodereader.cpp
specularreflectionreduction.cpp
superresolutioncode.cpp
variouscodereadings.cpp

Function Map

- ImageBufId

Compilation information

Synopsis

Read the code occurrence(s) in an image.

Syntax

void McodeRead(

MIL_ID ContextCodeId,	//in
MIL_ID ImageBufId,	//in
MIL_ID ResultCodeId	//in

)

Description

This function searches for code occurrences in an image, as specified in the code context, and writes the results in the specified result buffer. The code context's control settings determine how to perform the operation. Retrieve results using McodeGetResult().

Since the global context settings are required, McodeRead() requires that you pass a code context identifier, and not a code model identifier. The code context passed to McodeRead() can contain multiple code models depending on their code type (see McodeModel() for details). McodeRead() can read one or more occurrences of 1D and Data Matrix code models; for other types of code models, McodeRead() can read at most one occurrence.

It is strongly recommended to use a region of interest (ROI), set using MbufSetRegion(), with read operations, especially if your image contains more code occurrences than your context is configured to read; otherwise, MIL will randomly select which code occurrences to read, up to the specified number, from among all the code occurrences in the image. Reading only a portion of your source image is also recommended because it achieves a fast and robust read operation if your image contains other information besides the code occurrences. Note that, if your target image has an ROI, you can have the nominal angle set to the same angle of the target image's ROI, using McodeControl() with M_SEARCH_ANGLE set to M_ACCORDING_TO_REGION.

If you have associated the target image with a camera calibration context, you can specify that certain input settings be interpreted in world units. To do so, use McodeControl() with M_SCANLINE_INPUT_UNITS, M_DOT_SPACING_INPUT_UNITS, M_FINDER_PATTERN_INPUT_UNITS, M_SEARCH_ANGLE_INPUT_UNITS, and/or M_CELL_SIZE_INPUT_UNITS set to M_WORLD. Note that if you set any of these constants to M_WORLD but you don't pass McodeRead() a calibrated target image, the function will generate an error.

Before performing a read operation, certain control types might have to be set globally for the entire code context or individually for each code model in McodeControl(). When reading multiple occurrences of a Data Matrix code model, setting one or more of these values and reducing the search speed (using McodeControl() with M_SPEED) will produce more robust results.

Control type	Notes
M_CELL_NUMBER_X, M_CELL_NUMBER_Y	For 2D code types only, improves the robustness of the operation.
M_CELL_SIZE_MIN, M_CELL_SIZE_MAX	To improve the robustness of the read operation for some code types, especially Data Matrix and Maxicode. Note that MIL might have difficulty reading code occurrences if the cell size is less than 2 pixels, even if the size is specified.
M_ENCODING	For code types where M_ANY is not supported.
M_ERROR_CORRECTION	For code types where M_ANY is not supported.
M_FOREGROUND_VALUE	This control type is essential for all code types, and the image will not be decoded if the foreground value is not correctly set.
M_SEARCH_ANGLE, M_SEARCH_ANGLE_DELTA_NEG, M_SEARCH_ANGLE_DELTA_POS	If the code occurrences to read are not within 5° of the horizontal axis, and/or if the code occurrences have bearer bars.
M_STRING_SIZE_MIN and M_STRING_SIZE_MAX	For the M_BC412 code type, the string size must be specified.
M_SUB_TYPE	For M_COMPOSITECODE and M_GS1_DATABAR code type, specifying the code sub-type can help increase the speed of read operations.

Note that if the image contains Structured Append sequence of separate but logically linked ECC 200 code occurrences, MIL will treat the code occurrences as separate, independent code occurrences.

Note that this function reference has not been updated for a MIL system added during a MIL update. Refer to the MIL system's release note to see which MIL system’s documentation you should use in its place and any possible differences.

Parameters

This function is not supported on the selected boards.

This function reference has not been updated for the selected MIL system. To show the content of this page, choose a second MIL system; refer to the MIL system's release note to see which MIL system’s documentation to choose and any possible differences.

Parameters

ContextCodeId

Specifies the identifier of the code context.

ImageBufId

Specifies the 8-bit unsigned 1-band image buffer in which to search.

This image buffer can only have a rectangular region of interest (ROI) defined using MbufSetRegion() (with or without rotation). In addition, the region must be defined in vector format from a 2D graphics list (M_VECTOR or M_VECTOR_AND_RASTER). An error will be generated if the ROI is only in raster format (M_RASTER) or a non-rectangular shape.

ResultCodeId

Specifies the result buffer in which to write the results of the read.

Compilation information

Header	Include mil.h.
Library	Use mil.lib; milcode.lib.
DLL	Requires mil.dll; milcode.dll.