Read cards or tags

VTAP50 and VTAP100 are primarily designed to read mobile passes, not cards and tags. You can choose to allow VTAP reader to read particular NFC or MIFARE Classic card or tag types in addition to mobile passes, by making changes in config.txt.

Example: Changes to config.txt to allow NFC or MIFARE Classic card or tag types to be read

Copy

!VTAPconfig

NFCType2=N                
NFCType4=D
NFCType5=U
MIFAREClassic=B

; Use =U or 1 to permit a particular card type UID to be read
; =N or 2 to read NDEF records (NFC Type 2 or 4, not MIFARE Classic) 
; =B or 3 to read/decode memory blocks on MIFARE Classic, NFC Type 2 or 5
; =D can be used for NFCType4 to read DESFire cards
; =0 is disabled (default)

Note: Don't forget that you also need a setting such as KBSource=A1 to send this card/tag data, in addition to mobile pass data, over your preferred interface.

This table will help you find valid setting combinations:

Types of data from different card/tag types
	Compatibility
Card/tag type	UID (=U)	NDEF (=N)	Block data (=B)	Secure data (=D)
NFC Type-2/MIFARE Ultralight/NTAG			(AES)
NFC Type-4/DESFire/ Host Card Emulation				(EV1, DES/AES)
NFC Type-5/ICODE			(up to 255 bytes)
MIFARE Classic			(single block)

There are advanced settings such as NDEFTagExtractType and NDEFTagExtractID described in the NFC card or tag settings, which allow you to further extract the data that will be read.

When blocks of data are read from cards or tags, you may also want to set some of the parameters prefixed TagRead, or TagWiegand to Extract only part of the card or tag data.

You can also upload keys to read secured data from DESFire cards. This option is addressed in Read secured data from DESFire cards or tags.