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...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

BitPosition inSegmentField26 No BlockWrite UserAddressAlignmentDescriptionThis bit is used to indicate if the tag memory architecturehas hard block boundaries in the USER memory bank.If the value is zero the tag has hard block boundariesin the USER memory bank. The tag will not acceptBlockWrite commands that start in one block and endin another block. These block boundaries aredetermined by the max block size and the startingaddress of the first full block. All blocks have thesame maximum size.If the value is one the tag has no block boundaries inthe USER memory bank. It will accept allBlockWrite commands that are within the memorybank.31 – 27 [RFU] These bits are RFU and should be set to zero.39 –32 Size of BlockErase40 Variable SizeBlock Erase48 – 41 Block Erase<strong>EPC</strong> AddressOffsetMax block size that the tag supports for the BlockErasecommand. This value should be between 1-255 if theBlockErase command is described in this field.This bit is used to indicate if the tag supports BlockErasecommands with variable sized blocks.If the value is zero the tag only supports erasingblocks exactly the maximum block size indicated inbits [39-32].If the value is one the tag supports erasing blocks lessthan the maximum block size indicated in bits [39-32].This indicates the starting address of the first full blockthat may be erased in <strong>EPC</strong> memory bank.Copyright ©2005- 2011 <strong>GS1</strong> AISBL, All Rights Reserved. Page 123 of 218

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

Saved successfully!

Ooh no, something went wrong!