Printronix SL4M Reference Manual page 55

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 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. The NOMOTION parameter of the CREATE command
is used primarily in RFID applications. Refer to "CREATE"
in the IGP/PGL Programmer's Reference Manual .
Example 1
The following example programs an SGTIN–64 value
into the RFID tag that is embedded in a 4x6 smart
label. Assume that the SGTIN–64 value is provided as
a single number.
~CREATE;SGTIN–64;432
RFWTAG;64
64;H;*87D0034567ABCDEF* /EPC number
STOP
END
~EXECUTE;SGTIN–64;1
~NORMAL
RFWTAG
55