Data Layer Reference

All nodes live under the application’s base path:

hdvisionsystems/lumiscan-dmc-reader/

The paths below are given relative to it. The whole public surface of this version is four nodes.

Node tree

hdvisionsystems/lumiscan-dmc-reader/
├── input/
│   ├── image-address        (string)      address of the image node to read
│   └── parameter            (flatbuffers) detection parameters
├── execute                  (method)      read every Data Matrix code in that image
└── output/
    └── results              (flatbuffers) one entry per code found

Input

Node Type Access Description

input/image-address

string

read, write

Address of the Data Layer image node to read. The reader appends /data, /width, /height and /pixel-type. Empty by default, which makes a run fail until it is set.

input/parameter

flatbuffers

read, write

Detection parameters, type types/hdvisionsystems/lumiscan-dmc-reader/code_detect_parameters. See the note below.

input/parameter carries no settings in this version — its DetectionParameters table is empty. The node exists so that tuning can be added without changing the node tree. Writing to it changes nothing about how a code is read.

Method

Node Blocking Effect

execute

Yes

Reads the image at input/image-address and writes every Data Matrix code found to output/results. Takes no argument — write an empty value.

Output

Node Type Access Description

output/results

flatbuffers

read

Every code found by the last successful run, type types/hdvisionsystems/lumiscan-dmc-reader/code_detect_result. Empty array if the image held no code. See The Result.

Not present in this version

Operators coming from the other LumiScan applications should know what this one does not publish:

  • No status node. There is no status-code or status-text; a failed run is reported in the application log only, and leaves output/results holding the previous run’s codes.

  • No data identifier. There is nothing to echo back, so a result cannot be correlated with the request that produced it.

  • No result image. The application renders nothing — no result-image node and no plot method. Use LumiScan Cockpit to see the codes drawn on the picture.

  • No modules. One reader per installation, at the single base path above.

  • No region of interest. Every run searches the whole image.