I am also using RC522 readers with Arduino for an application and bought this unit as a way to check cards/tokens. It only reads the card ID and not other card data. e.g. good for use as a simple ID token reader. This acts as an input device - so will send the CSN/ID of the card as if it had been typed in from a keyboard e.g. focus needs to be on an input box when a card is read. The card ID is the only thing read, this is 4 bytes in decimal format. The card ID bytes are in reverse order with this USB Reader compared to my RC522 readers. I used a decimal to hex function to show the individual byte values as hex, then reversed the order. The ID then lines up with my reader units. Bottom line is you need to decide on the format of the card number for your application and adjust in code as needed. It does what I waned it to do - a card is read 5 cm away and token 3 cm away.

I am also using RC522 readers with Arduino for an application and bought this unit as a way to check cards/tokens. It only reads the card ID and not other card data. e.g. good for use as a simple ID token reader. This acts as an input device - so will send the CSN/ID of the card as if it had been typed in from a keyboard e.g. focus needs to be on an input box when a card is read. The card ID is the only thing read, this is 4 bytes in decimal format. The card ID bytes are in reverse order with this USB Reader compared to my RC522 readers. I used a decimal to hex function to show the individual byte values as hex, then reversed the order. The ID then lines up with my reader units. Bottom line is you need to decide on the format of the card number for your application and adjust in code as needed. It does what I waned it to do - a card is read 5 cm away and token 3 cm away.

I am also using RC522 readers with Arduino for an application and bought this unit as a way to check cards/tokens. It only reads the card ID and not other card data. e.g. good for use as a simple ID token reader. This acts as an input device - so will send the CSN/ID of the card as if it had been typed in from a keyboard e.g. focus needs to be on an input box when a card is read. The card ID is the only thing read, this is 4 bytes in decimal format. The card ID bytes are in reverse order with this USB Reader compared to my RC522 readers. I used a decimal to hex function to show the individual byte values as hex, then reversed the order. The ID then lines up with my reader units. Bottom line is you need to decide on the format of the card number for your application and adjust in code as needed. It does what I waned it to do - a card is read 5 cm away and token 3 cm away.

Works very well (from about 4cm already), but watch out for the output. As I'm from Belgium, my keyboard layout was AZERTY, which gives strange results in scanning output, make sure it's set to QWERTY. Apart from that, read the other review in here that explains how the ID is read, that helpen me to figure out how to parse the data.

Works very well (from about 4cm already), but watch out for the output. As I'm from Belgium, my keyboard layout was AZERTY, which gives strange results in scanning output, make sure it's set to QWERTY. Apart from that, read the other review in here that explains how the ID is read, that helpen me to figure out how to parse the data.

Works very well (from about 4cm already), but watch out for the output. As I'm from Belgium, my keyboard layout was AZERTY, which gives strange results in scanning output, make sure it's set to QWERTY. Apart from that, read the other review in here that explains how the ID is read, that helpen me to figure out how to parse the data.