---
title: "Release Notes: v1.0.0"
product: "LumiScan Barcode Reader"
component: "lumiscan-barcode-reader"
version: "1.0.0"
display_version: "1.0.0.5"
latest_version: true
language: "en"
url: "https://docs.hdvisionsystems.com/en/lumiscan-barcode-reader/1.0.0/release-notes/v1-0-0.html"
---

# Release Notes: v1.0.0 – LumiScan Barcode Reader

First functioning release of LumiScan Barcode Reader.

## New

**Barcode reading.** `execute` reads the image named by `input/image-address` and publishes what it found to `output/results`. Each code is reported with its decoded `text`, the `center` and the `polygons` outlining it in the image, and a `score`.

**The whole linear family in one call.** The reader is configured for ZXing’s *linear* symbology set rather than one format, so Code 128, Code 39, EAN-13 and UPC-A are all read by the same call, among others. The symbology does not have to be identified in advance.

**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 `bar-code` and draws a rectangle around each code, labelled with the decoded text and the score.

## Worth knowing

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

**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 barcode.

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

## Earlier releases

**Version 0.0.1** — stub. The node tree was registered, and `execute` did no reading.