Release Notes: v1.1.0
First functioning release of LumiScan Aztec Code Reader. Earlier versions registered the application’s Data Layer nodes but did no reading.
New
Aztec code 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.
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 aztec-code and draws a
rectangle around each code, labelled with the decoded text and the score.
Changed
The application moved from hdvisionsystems/lumiscan-aztec-code to
hdvisionsystems/lumiscan-aztec-code-reader, the name the other code readers already use. Anything
addressing the old path — a PLC, a REST client, a saved app state — must be repointed; the node names
below the application are unchanged.
Worth knowing
input/parameter has no settings yet. It is published for detection settings, but the schema
carries no fields: detection runs with fixed settings, and the node is there so settings can be added
without changing the address.
The outcome of a run is reported in the application log rather than on a node — there are no
output/status-code and output/status-text nodes on this application. A failed run leaves
output/results holding the previous run’s codes. An empty result is unambiguous: the image was read
and held no Aztec code.