Primary Reader
Within a group, one reader is defined as the primary reader. When the primary reader is triggered (regardless of what
type of trigger it uses), all the readers in the group are also triggered. For self-trigger mode, you must designate the
primary reader explicitly. For externally triggered modes (single, burst, and continuous), whichever reader receives the
trigger is designated the primary reader for that acquisition. (In most cases, only a single reader in the group will be
connected to the external trigger.)
To account for network latency, you specify a trigger delay for the primary reader in the group. When the primary reader
is triggered, it immediately sends triggers to the other group members, but delays its own acquisition for the specified
delay, allowing the trigger signal to reach the other readers. You can also configure a separate trigger timeout, which will
cause the primary reader to wait for a specified period of time for secondary readers to send data before collecting the
results and transmitting them.
After a read attempt, only the primary reader transmits a result. It combines all of the available results from the other
readers in the group in the same way that multicode results are combined.
Secondary Readers
In many applications, the multi-reader sync configuration is set to trigger the secondary readers whenever the primary
reader is triggered. If the secondary readers are configured for Self triggering, then they will also trigger whenever they
detect a code. In this case, the primary reader will generate and transmit a read result whenever any reader detects a
code. This result aggregation greatly simplifies multiple reader operation.
Data Formatting
When the reader is triggered, the result string will be formatted as you specified, before it is transmitted to the primary
reader for aggregation. Note, however, that you have to check Standard Formatting Enabled for the primary reader and
supply the formatting tokens you want to use for the secondary readers. Any data formatting that you specify for the
primary reader will be applied to the formatted result strings produced by the secondary readers. The Format Data pane
includes a token that allows you to insert the name of the reader generating the result string; you can use this to identify
which reader produced which result.
Limitations
l No image buffering and recording is supported for any reader that is part of a group.
l Presentation mode triggering is not supported.
l Multi-Reader Sync triggering only works correctly if the Primary and the Secondary readers use specific, allowed
combinations of trigger modes. They are the following:
l Self/Self
l Single/Burst, Single/Single, Burst/Burst, Burst/Single
l Manual/Continuous, Manual/Manual, Continuous/Continuous, Continuous/Manual
Synchronized Acquisition
Synchronized Acquisition is only available for the DataMan 300, 360, 370, and 470 readers with an -Moption, and the
DataMan 503. In Single, Burst, Continuous, and Self trigger modes, it is possible to synchronize image acquisition on
multiple devices using the synchronization interface.
Synchronization allows using one shared strobe illumination to expose all sensors simultaneously. You can synchronize
multiple readers, with optionally triggering them in a defined sequence to avoid that opposing readers blind each other.
161
Operations Guide
To Next Page
Loading...
