FAQ

Yes. On ctrlX OS (ctrlX CORE or ctrlX IPC) it uses the ctrlX Data Layer; on a PC (Windows 11 or Ubuntu 24.04) it uses LumiScan Keryx, the Data Layer of HD Vision Systems for PCs. The node addresses, types and behaviour are the same on both, so a program written against one works against the other.

Data Layer Reference, ctrlX Data Layer and LumiScan Keryx

It reads ECC 200 Data Matrix codes, the square-module standard used for part marking and direct part marking. Every code found in the image is reported; there is no limit of one per run. No template, reference picture, training step or configuration is needed: you give the reader the address of an image and call execute.

Description

The reader does not talk to a camera itself. It reads the image node named in input/image-address, published by another application: on ctrlX OS one on the same device (remote Data Layer access is not supported), on a PC one connected to the same LumiScan Keryx. Normally this is LumiScan Cam Driver, for example hdvisionsystems/lumiscan-cam-driver/camera1/output/image. The node must provide data (raw, uncompressed uint8 pixel data), width, height and pixel-type (GenICam pixel format name). Give the address of the image node itself, not of its data child: the reader appends /data, /width, /height and /pixel-type.

Requirements, Reading a Code

Mono8, Mono12, RGB8, RGB12, BGR8, BGR12, Bayer_GR8, Bayer_RG8, Bayer_GR12 and Bayer_RG12. The name is matched without regard to case, and the underscore may be left out of the Bayer names (BayerGR8 and bayer_gr8 are the same format). Bayer images are converted to colour before the search. Any other pixel format is refused, and the run produces no result. The image data must be at least width x height x bytes-per-pixel bytes for the declared format; a shorter buffer is refused.

Requirements

All paths are relative to hdvisionsystems/lumiscan-dmc-reader.

Reading a Code

output/results is a flatbuffer (CodeDetectResultArray.results) with one entry per code: center (a Point2f with x and y in image pixels), text (the decoded contents), score (how confident the read is) and polygons (the corner points outlining the code). On ctrlX OS, over the ctrlX REST API, the numbers come back quoted, as strings, so parse them as numbers. center and text are always present; polygons may be absent for an entry, which means no outline was given, not an error.

The Result

This reader publishes no status-code or status-text node and echoes no identifier. A run fails if the image cannot be read: no address set, an address that does not resolve, a missing or short data buffer, or an unsupported pixel format. A failed run leaves output/results untouched, still holding the previous run’s codes.

Check the application log (on ctrlX OS, the system log), where the reason is written, or read output/results before and after the run and compare.

Reading a Code, Data Layer Reference

No, not in this version. input/parameter carries no settings (its DetectionParameters table is empty), so writing to it changes nothing; the image stream does not read it either. There is no region of interest: every run searches the whole image. There are no modules: one reader per installation, at a single base path. There is also no result image; use LumiScan Cockpit to see the codes.

Data Layer Reference

Open LumiScan Cockpit. It lists the reader as a view named datamatrix-code and draws a rectangle around each code, labelled with the decoded text and the score. A code that was located but not decoded has no text and is labelled with its score alone.

The Result

Reading is synchronous: the write to execute returns when the search has finished. How long that takes depends on the image size, since the whole image is searched on every run.

Requirements

Yes, as an experimental function. The reader subscribes to the stream of one camera of LumiScan Cam Driver and reads every Data Matrix code in each frame as it arrives, exactly as execute reads an image. All paths are relative to hdvisionsystems/lumiscan-dmc-reader.

Reading Codes on an Image Stream, Streams

In dmc-reader.json in the application’s configuration directory: on ctrlX OS /var/snap/rexroth-solutions/common/solutions/activeConfiguration/lumiscan-dmc-reader, on Windows C:\ProgramData\HD Vision Systems GmbH\LumiScan Vision Suite\lumiscan-dmc-reader\etc\lumiscan-dmc-reader (or %APP_RESOURCE_DIR%\etc\lumiscan-dmc-reader). control/subscribe/execute and control/unsubscribe/execute save what they apply there, and after a restart a reader that streamed streams again at once. On a PC, lumiscan-dmc-reader --generate-settings <folder> writes an example to start from.

Kept in the settings file

If an Advanced licence is available, the application uses it automatically. If none is available, it runs with Standard functions rather than refusing to start.

Requirements, Licensing FAQ

One licence seat covers the reader, since there is one reader per installation. Purchase routes:

Requirements, Licensing FAQ

See the site-wide LumiScan FAQ. Contact HD Vision Systems customer success at customer.success@hdvisionsystems.com or +49 6221 6721905; for licences, licenses@hdvisionsystems.com.

Licensing FAQ