Printronix T6000 Reference Manual page 31

NOTE: 1. The RFWTAG command cannot be mixed with RFWRITE in the same form.
2. Each field structure must be specified in a single line and in the order it appears in the RFID tag
from MSB bits to LSB bits (left to right). The sum of all the field lengths must match the size of
the tag.
3. The host data are read in as ASCII characters. They would be converted to binary
representation for the base field on the field format. Therefore, if the converted value is larger
than the maximum value that a field can hold, an error will be reported. If the data value is
smaller than the specified field length, on the other hand, the field will be padded to the left with
zero bits.
4. Unlike the Alpha and Barcode command which use STEPMASK for incremental data,
RFWTAG uses the STEP which will increment or decrement at bit level.
5. 432 IGP dots in the ~CREATE line specifies a 6 inch label. 6 inches = 432 (IGP dots)/72 (dpi)
Use 144 for 2 inch labels and 288 for 4 inch labels.
6. ACS and KIL are similar to other memory banks. ACS contains the passcode which is used for
LOCK and UNLOCK operations. KIL contains the killcode which is used to kill a tag. The user
can write to or read from KIL memory bank, but the functionality of killing a tag is not currently
applicable. Also, once ACS and KIL are locked, both cannot be written to or read from. For
other memory banks, EPC, USR, and TID, once locked, they can be read from but not written
to.
7. There are two ways to program the ACS memory area. One is to write to the ACS memory area
directly with RFWTAG. The other is to use the LOCK option while writing to other memory
banks. If ACS is not previously locked, then LOCK option will lock the memory bank and also
write the passcode to ACS and lock ACS. When write to ACS with RFWTAG, ACS is not
automatically locked. To lock ACS, use LOCKn with RFWTAG, where the passcode (n) should
be the same as the write data to ASC.
8. There is only one passcode, the content of ACS memory bank, for each tag. The same
passcode is used to lock or unlock any memory bank in that tag.
9. For LOCKn and UNLOCKn, the passcode (n) (which includes the dynamic format <DFn>) does
not accept incremental data. This also applies to the ACS and KIL memory banks. The write
data to the ACS and KIL memory banks do not accept incremental data because the ACS
memory bank contains passcodes for LOCK and UNLOCK operations, and the KIL memory
bank contains a killcode to kill a tag. Incremental data do not apply to passcodes or killcodes.
10. When LOCK<DFn> and UNLOCK<DFn> are used in the same form with the same dynamic
data (the passcode), the dynamic format <DFn> needs to be a different dynamic number for
LOCK and UNLOCK since it is designed with a unique dynamic number that can be linked to
only one object type. In this case, LOCK is linked to RFWTAG object and UNLOCK is linked to
RFRTAG object. Although both options use the same passcode, the dynamic format needs to
be in a different dynamic number in the same form.
11. Because PC field is related to EPC field, when PC RFWTAG is used in the form, it must be
followed immediately by EPC RFWTAG, or else an error will be reported. Also, by specification,
the first 5 bits of PC data need to comply with the length of EPC data, or else an error will be
reported. For example, for 96 bits EPC, the 5 bits of PC data is 00110. For 64 bits EPC, the first
5 bits of PC data is 00100. Also, LOCK option is not and will not be supported for PC field, since
PC field works with EPC field (which already supports LOCK option).
12. Both LOCK and PERMALOCK requires the user to enter the password. Once the tag is
permanently locked with the PERMALOCK command, it cannot be unlocked again; the tag can
only be read from and never be written to once it is permanently locked. On the other hand,
after the tag is locked with the LOCK command, it can be unlocked again with the same
password.
31