User manual

112
• Value functions Inc, Dec, Transfer and Restore are not supported by the reader.
Programming Tickets
RFID extensions have been added to the FGL programming language allowing users to program the tag data
with the same ease as defining the data for a bar code ticket or label. RFID commands can be used in
conjunction with any standard FGL programming command. The RFID commands can be used to read the
unique ID number of each ticket, read/write tag data and send that data to the Host.
RFID tags are based on an EEPROM technology that requires time to be programmed. As mentioned before,
you may notice a slight printing delay between tickets. This time is necessary to ensure consistent reliability.
Occasionally, a ticket may need to be written and verified more than once. This retry period will increase the
delay between tickets. The number of retries can be set using an RFID command. Another factor that can be
changed by the user, is the period of time that the printer will wait for a response from the RFID encoder. This
will vary among different stocks and RFID technologies. You should only increase the timeout amount if
‘timeout error’ void tickets are being printed.
FGL RFID Programming Extensions:
READ RF CARD UNIQUE TAG ID (SERIAL NUMBER) COMMAND - <RFSN ‘format’, ‘send option’>
The printer returns the TID (serial number) for the selected tag. The number of bytes returned depends
on the type of tag selected.
Each I-Code (SL2) ticket contains a unique 8 byte serial number starting with E00401. This number can be read
from the ticket and either printed or sent to the Host.
Each MIFARE Ultralight ticket contains a unique 7 byte serial number. This number can be read from the ticket
and either printed or sent to the Host.
Each MIFARE 1K ticket contains a unique 4 byte serial number. This number can be read from the ticket and
either printed or sent to the Host.
The ‘format’ field values are as follows:
1 - Binary format (1 byte/value) Data is used as is. For example, the character ‘1’ (31h) is stored or sent as
31h. Use this format for programming or reading printable Text characters like names and addresses.
2 – ASCII format (2 bytes/value) Data is represented as the Hex value of each nibble. For example, a data
value of 1 (01h) is stored or sent as 30h (ASCII character ‘0’) and 31h (ASCII character ‘1’). Use this format for
programming or reading non-printable characters like serial numbers or data.
Note the difference between the character ‘1’ (31h) and the byte value of 1 (01h). You use Binary format to
send a character ‘1’ and ASCII format to send a byte value of 1.
The ‘send options’ are as follows:
0 – send data to ticket
1 – send data to host
2 – send data to ticket and Host
The <RC10,10><F2><RFSN2,2> command would be used to read the ticket’s serial number in ASCII format
and print it in font2 at position 10,10 on the ticket as well as sending it to the Host. For example, if the 7 byte
serial number was comprised of values 04h,0Ch,65h,D1h,10h,00h,40h the printer would print 040C65D1100040
on the ticket and send it to the Host as 30h,34h,30h,43h,36h,35h,44h,31h,31h,30h,30h,30h,34h,30h.
REQUEST RF CARD STATUS COMMAND
- <RFSN0> (Note: this is a zero).