---
title: "Release Notes: v1.1.0"
product: "LumiScan DMC Reader"
component: "lumiscan-dmc-reader"
version: "1.1.0"
display_version: "1.1.0.6"
latest_version: true
language: "en"
url: "https://docs.hdvisionsystems.com/en/lumiscan-dmc-reader/1.1.0/release-notes/v1-1-0.html"
---

# Release Notes: v1.1.0 – LumiScan DMC Reader

First functioning release of LumiScan DMC Reader. Version 1.0.0 registered the application’s Data Layer nodes but returned a fixed placeholder result, so nothing below was usable before.

## New

**Data Matrix reading.** `execute` searches a camera image for ECC 200 Data Matrix codes and reports every one it finds. No reference picture and no training step: the only input that changes between runs is which image to read.

**A result per code**, in `output/results` — the decoded text, the centre in image pixels, a confidence score, and the corner points outlining the code. A run that found nothing publishes an empty array rather than an error.

**Any image source on the same ctrlX CORE.** `input/image-address` names the image node to read, so the reader follows whatever application publishes the picture. Mono, RGB, BGR and Bayer formats are accepted at 8 and 12 bit, and Bayer images are converted to colour before the search.

**Drawn results in LumiScan Cockpit**, which lists the reader as a view named `datamatrix-code` and draws a rectangle around each code, labelled with the decoded text and the score.

## Worth knowing

**A failed run leaves the previous result in place.** This version publishes no status node and echoes no identifier, so `output/results` alone does not distinguish a fresh read from a stale one. The reason for a failure is written to the application log. An **empty** result is unambiguous: the image was read and held no Data Matrix code.

**`input/parameter` has no settings yet.** Its `DetectionParameters` table is empty; the node exists so that tuning can be added later without changing the node tree.

**Every run searches the whole image.** There is no region of interest, so run time scales with the image size.

## Earlier releases

**Version 1.0.0** — stub. The node tree was registered and `execute` returned a fixed placeholder result.