Apr 01, 2015  If you are using NFC (Near Field Communication) Mifare in your application, you should be careful while using NFC Mifare UID (Unique IDentification also know as Card Serial Number) of NFC card. When any card is manufactured, it will be assigned a card serial number and it must be there if there is no any data. Serial Mifare® Reader (RS232 / UART / I2C). SM2300 is a compact, ready-to-go, OEM serial reader that includes all neccessary components for 13.56 MHz RFID Mifare® Reader/Programmer including the PCB antenna, on board 5V regulator, I/O pins, LEDs and a buzzer.

DOWNLOAD AND READ THE DOCUMENTATIONS

First thing to do is to obtain the documentation of the card from the manufacturer (NXP in this case) and the Prox’N’Roll developer’s reference manual.

From the card’s functional specifications, we can see that the memory is structured in 16 pages of 4 bytes. The four first pages (0-3) contain special bytes: so, we’ll only cover pages 4 to 16.

STEP BY STEP PROCEDURE

The goal is to read and write the card memory.

READ BINARY

In the developer’s reference manual, the READ BINARY instruction is described in §2.2.4 at the time of this writing.

The APDU is :

• CLA: FF
• INS: B0
• P1: Address MSB
• P2: Address LSB
• Lc: not needed
• Data in: not needed
• Le: number of bytes to be read

The specifics to read Mifare Ultralight cards are detailed in §4.3.3.a (at the time of this writing).
Here, we can see that :

• P1 must be 00
• P2 is the address of the first page to be read
• Le must a multiple of 4.

We want to read the whole memory, starting from page 4: this means we want to read 12 pages of 4 bytes, so 48 bytes (ie: 30 in hexadecimal).
So the APDU is :
FF B0 00 04 30

To send this APDU, please use our PC/SC Diagnostic tool, available on our main site (QuickStart for PC/SC).

Put the card on the reader: its ATR prints. To understand what this means, you can check §4.1.2 (at the time of this writing) in the developer’s reference manual.

Now, double-clic on the line corresponding to the reader and enter the above-mentioned APDU :

Clic on Transmit, or press “Enter”: the APDU is sent to the card and its response is printed in the bottom.

The card has obviously been previously written and the ASCII translation is provided: “Mifare Ultralight card, used with Prox’N’Roll”.
Please note that the card’s reponse ends with “90 00”, which means success.

UPDATE BINARY

In the developer’s reference manual, the UPDATE BINARY instruction is described in §2.2.5 at the time of this writing.

The APDU is :

• CLA: FF
• INS: D6
• P1: Address MSB
• P2: Address LSB
• Lc: Lenght of Data In
• Data in: Bytes to be written
• Le: not needed

The specifics to write Mifare Ultralight cards are detailed in §4.3.3.b (at the time of this writing).
Here, we can see that :

• P1 must be 00
• P2 is the address of the unique page to be written
• Le must be 4.

We want to replace “Prox’N’Roll” by “SpringCard” in the card memory, so we first have to determine which pages must be updated. Remember that Le must be 4 : this means that we can write exactely 4 bytes at a time (one page), no more, no less.

To determine the content of each page, just use the READ BINARY APDU.
For example, for page 12, the APDU should be : FF B0 00 0C 04

Using those commands, we can see that:

• content of page 12 (0x0C) is 68 20 50 72 (in ASCII : “h Pr”)
• content of page 13 (0x0D) is 6F 78 27 4E (in ASCII: “ox’N”)
• content of page 14 (0x0E) is 27 52 6F 6C (in ASCII: “‘Rol”)
• content of page 15 (0x0F) is 6C 00 00 00 (in ASCII: “l” followed by invalid characters)

So, we’ll need to change 4 pages : pages 12, 13, 14 and 15.

SpringCard in ASCII is : “53 70 72 69 6E 67 43 61 72 64”

The 4 APDUs (one for each page) should be:

• page 12: FF D6 00 0C 04 68 20 53 70 (the first two bytes remain unchanged)
• page 13: FF D6 00 0D 04 72 69 6E 67
• page 14: FF D6 00 0E 04 43 61 72 64
• page 15: FF D6 00 0F 04 00 00 00 00 (we replace the first byte)

Enter those APDUs and click on “Transmit” :

Operation is successful if the card answers 90 00.

Now, you can read back the whole memory, using FF B0 00 04 0C:

We can see that “Prox’N’Roll” has been replaced by “SpringCard” in the card memory.

Trade items between your characters or store the items offline in your private vault. Create an unlimited number of vaults with any name you want. All vaults are stored in My Documents My Games Titan Quest TQVaultData. Split potion stacks apart. Makes backups of all files before modifying them. If you encounter any errors, you can find. Free titan quest vault download. Games downloads - TQVault by bman654 and many more programs are available for instant and free download. TQVault Anniversary Edition By North and 2 collaborators TQVaultAE is an external tool for Titan Quest Anniversary Edition that allows you to store and search your items outside of the game. Adds new functions such as item trading between characters in Titan Quest. Download Review Comments (4) Questions & Answers (2) Download latest version from Software Informer. DOWNLOAD NOW 16.6 MB. See the report or download other versions of TQVault. Fail to download? Try Free Download Manager (FDM) Latest versions of TQVault.

If you are using NFC (Near Field Communication) Mifare in your application, you should be careful while using NFC Mifare UID
(Unique IDentification also know as Card Serial Number) of NFC card.

When any card is manufactured, it will be assigned a card serial number and it must be there if there is no any data.

When you try to fetch that UID using Android SDK NFC tag technology, it will return you UID in reverse order.

Generally when card ia manufactured, bytes are stored in LSB (Least Significant Byte) order while when Android read card serial number, it will read in MSB(Most Significant Byte) fashion.

For example. Any card has UID “12345678” then in MSB fashion, it will be like “78563412“.
So you need to convert this order from MSB to LSB.

Following short of code will help you to do this.