Avery Dennison RFID - Manual (Page 48)

HowToRFID
Revision: 13 Date: 31 August 2009
Page 48 of 53
#G <<< syntax for FW-versions >= Vx.33 >>>
#VDE/EPC96_BD/DualToBin(
PadLeft(EPC_BS_Header, "0",8)
+PadLeft(EPC_BS_Filter, "0",3)
+PadLeft(BinToDual(DecToBin(EPC_DV_Partition)), "0",3)
+PadLeft(BinToDual(DecToBin(EPC_DV_CompanyPrefix)), "0",24)
+PadLeft(BinToDual(DecToBin(EPC_DV_SerialRef)), "0",34)
+PadLeft(EPC_BS_Free, "0",24)
)#G
#G <<< end of version depending expressions >>>
#G --- write EPC-96 to transponder
#SRF2#G set RFID chip access definition -> EPC
#VW/T/EPC96_BD#G
#G --- write SSCC and EPC96 on label
#SF106//#G set fixed Font
#SS102//40#G set scalable Font
#T5#J20#VW/L/"SSCC (dec)= "+SSCC#G
#T5#J14#VW/L/"EPC (hex)= "+BinToHex(EPC96_BD)#G
#Q1#G
The example above will write the EPC 315613D8FCB2DFB87E000000 to the tag (and print on the label).
6.2.7 EPC/EAN128 shipping label (SSCC + SSCC-96) + automatic transfer from Barcode SSCC (NVE) to
EPC using a scanner
This sample shows how a SSCC (NVE) read from a barcode is transformed to a SSCC-96 EPC encoded following
the EPC tag data standards.
All of this is based on the variable data handling approach and shows the potential of this for bringing “intelligence”
inside the printer.
A usage scenario like this is also known as “slap & ship” solution.
The sample job produces a label where the layout and data content follows the GS1 recommendation for an
EPC/EAN128 shipping label. The data printed is limited to the minimum required information: SSCC (NVE) -
human readable and EAN128 bar code, EPC logo. The printed EPC code is only for demonstration – it’s not
required on the shipping label.
The job is designed to be used a stand alone job to be loaded from a CF card, but by modifying the way to SSCC
(NVE) is defined (read in), the job can also be used as an regular print job.