Device Modes¶
Overview¶
The ItemEncode device has a few different device modes that it is capable of. By configuring the DeviceMode, the application is telling the ItemEncode device what to do when it encounters a tag.
Encode¶
The primary mode of an ItemEncode device. In the Encode mode, the ItemEncode device will attempt to encode any tags that it encounters. It will use the SerializationJob to decide what encoding operations will need to be performed to the tag and the OperationResponsibility to determine which of those encoding operations it is responsible for.
Verify Tag Chip Basic¶
In Verify Tag Chip Basic mode, the ItemEncode device will attempt to verify that any tags that it encounters have the correct EPC length. It will use the SerializationJob to determine what EPC length that the tag should be matched against.
Verify Tag Chip Data¶
In Verify Tag Chip Basic mode, the ItemEncode device will attempt to verify that any tags that it encounters have had all requested encode operations completed. Please note that this is specifically for final tag verification in a Pipeline System with upstream ItemEncode devices performing the encoding work. It will use the SerializationJob to decide what encoding operations should have been performed.
Inventory¶
In Inventory mode, the ItemEncode device will report all tags that it encounters. If specified in the InventoryJob, the device will also perform a read on user memory.
Operational Modes¶
Overview¶
Impinj ItemEncode has two primary types of Operational Modes. By configuring the OperationMode in the DeviceConfig, the application is controlling how long the ItemEncode device will continue to operate.
Continuous Mode¶
In Coninuous Operation Mode, the Impinj ItemEncode device will continue to operate until it receives a Stop signal from the network or GPI trigger. This mode is useful when encoding a continuous stream of tags.
Single Mode¶
In Single Operation Mode, the Impinj ItemEncode device will Stop after finishing the operations on a single tag. This is useful when there is only a single tag in the field of view. Because the device can assume that there is only a single tag, it can optimize the operations accordingly.
