11.08.2015 Views

GS1 EPC Tag Data Standard 1.6 - Indicod-Ecr

GS1 EPC Tag Data Standard 1.6 - Indicod-Ecr

GS1 EPC Tag Data Standard 1.6 - Indicod-Ecr

SHOW MORE
SHOW LESS
  • No tags were found...

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

31443145314631473148314931503151BitPosition inSegmentField7 SeparateLockbits8 Auto UMISupportDescriptionIf this bit is set it means that the tag supports lock bits foreach memory bank rather than the simplestimplementation of a single lock bit for the entire tag.If this bit is set it means that the tag automatically sets itsuser memory indicator bit in the PC word.9 PJM Support If this bit is set it indicates that the tag supports phasejitter modulation. This is an optional modulation modesupported only in Gen 2 HF tags.10 BlockEraseSupported11 BlockWriteSupported12 BlockPermaLock SupportedIf set this indicates that the tag supports the BlockErasecommand. How the tag supports the BlockErasecommand is described in Section 16.2.4. A manufacturemay choose to set this bit, but not include the BlockWriteand BlockErase field if how to use the command needsfurther explanation through a database lookup.If set this indicates that the tag supports the BlockWritecommand. How the tag supports the BlockErasecommand is described in Section 16.2.4. A manufacturemay choose to set this bit, but not include the BlockWriteand BlockErase field if how to use the command needsfurther explanation through a database lookup.If set this indicates that the tag supports theBlockPermaLock command. How the tag supports theBlockPermaLock command is described inSection 16.2.5. A manufacture may choose to set this bit,but not include the BlockPermaLock and User Memoryfield if how to use the command needs furtherexplanation through a database lookup.15 – 13 [RFU] These bits are RFU and should be set to zero.Table 44. Optional Command Support XTID Word16.2.4 BlockWrite and BlockErase SegmentIf bit eleven of the XTID header is set then the XTID shall include the four-wordBlockWrite and BlockErase segment. To indicate that a command is not supported, thetag shall have all fields related to that command set to zero. This SHALL always be thecase when the Optional Command Support Segment (Section 16.2.3) is present and itindicates that BlockWrite or BlockErase is not supported. The descriptions of the fieldsare as follows.Copyright ©2005- 2011 <strong>GS1</strong> AISBL, All Rights Reserved. Page 121 of 218

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!