User manual

113
This command can be sent by the Host after receiving a NAK (15H) to determine the cause of the error. The
printer sends back a single byte ASCII status indicating the status. A list of the status codes and errors are
shown at the end. Looking at the list you will see that different errors can have the same code. For example,
the printer will return a generic ‘C’ code for all command errors but displays the specific error message on the
LCD display.
Once a NAK has been sent the ticket is considered ‘Void’. This Void state remains in effect until the ticket is
printed, removed or an <RFC> command is sent (see next command). Any remaining RFID operations, even if
successful, will not change the Void state. If the ticket is printed, it will have the word ‘VOID’ printed on it along
with the original cause for the NAK.
Note: a NAK is sent after every failed RFID operation. If multiple operations are attempted it is possible to
receive multiple NAK’s. If the Request Status command is sent after a string of RFID commands, the printer will
only return the status code for the last operation. The status code remains in effect until a new RFID operation
completes, an <RFC> command is received, or the ticket is either printed or removed. The ‘status state’ is
different than the ‘Void’ state. It is always the status of the last RFID operation performed.
CLEAR ALL RFID ERRORS - <RFC>
As mentioned above, once an error has occurred the ticket will be in a ‘void’ state. You will no longer be able to
print a valid ticket using that tag. If for some reason you want to try another RFID operation using the same tag
you must clear the error state flags. Sending the <RFC> command will clear all the error states and return the
printer to the normal state.
READ RF CARD COMMAND - <RFR ‘format’, ‘starting block’, ‘number of bytes to read’ , ‘send option’>
The ‘format’ field uses the same values as explained in the RFSN command (1,2).
The ‘starting block number’ can range from 0-27 (I-Code2), 0-15 (MIFARE Ultralight) or 0-63 (MIFARE 1K)
The ‘number of bytes to read’ can range from 1-64 depending on starting block. Note: This is presently
a limitation of the reader. If you need to read more than 64 bytes, you must issue extra read commands.
Mifare 1K tags can only be read up to 16 bytes at a time.
The ‘send options’ are the same as described in the RFSN command.
The <RC10,10><F2><RFR1,4,12,0> command would be used to read 12 bytes starting at block 4 and print it in
Binary format in font2 at position 10,10 on the ticket. For example, if the 12 bytes starting at block 4 were
comprised of values 42h,4Fh,43h,41h,20h,53h,59h,53h,54h,45h,4Dh,53h the printer would print BOCA
SYSTEMS on the ticket.
WRITE RF CARD COMMAND - <RFW ‘format’, ‘starting block’, ‘lock option’>data bytes …..(CR-carriage
return) or command delimiter
On an I-Code2 card, blocks 0-27 (112 bytes) are available for user data.
On the MIFARE Ultralight card, blocks 4-15 (48 bytes) are available for user data.
On the MIFARE 1K, blocks 0-63 (768 bytes) are available for user data (some bytes unavailable).
Important: Data must be written in multiples of 4 bytes (16 for Mifare 1K). If not, remaining bytes will be
programmed to zero on the card.
The ‘format’ field uses the same values as explained in the RFSN command (1,2).
The ‘starting block number’ can range from 0-27 (I-Code2), 4-15 (MIFARE Ultralight) or 0-63 (MIFARE 1K)
The ‘lock option’ values are as follows: 0 – Do not lock data
1 – Lock data