Public platform independent Near Field Communication (NFC) library
You are not logged in. Please login or register.
Dear Roel,
I have recently bought 2 touchatag from the official store. I write you to confirm that the firmware is ACR122U102 (the same for tikitag). I have no idea how viewing the chip version but if i find, i tell you. Now you can complete your hardware table.
Have a nice day !
Thank you very much, I will update the table!
If you use the source-code from the SVN you will see the chip revision displayed when you start-up an example tool.
Thank you for the information : the command list return me : ACR122U102 - PN532 v1.4 (0x07).
So this is exaclty the same for tikitag (in fact this is just a commercial change !)
But the list command doesn't show me the 2 touchatag, only one ! So i can't use the relay command.
Do you know why ?
PS : a little suggestion : the usage (or just a "-h") would be very appreciate.
Thanks for your excellent work !
Just for precision, the two Touchatag are correctly loaded
> lsusb
Bus 002 Device 025: ID 072f:90cc Advanced Card Systems, Ltd ACR38 SmartCard Reader
Bus 002 Device 024: ID 072f:90cc Advanced Card Systems, Ltd ACR38 SmartCard Reader> pcsc_scan
PC/SC device scanner
V 1.4.15 (c) 2001-2009, Ludovic Rousseau <ludovic.rousseau@free.fr>
Compiled with PC/SC lite version: 1.5.3
Scanning present readers...
0: ACS ACR 38U-CCID 00 00
1: ACS ACR 38U-CCID 01 00So the question is : why this result ?
> ./list
Connected to NFC reader: ACR122U102 - PN532 v1.4 (0x07)The list command, tries to list the available tag. You are right this is confusing.
Did you placed a ISO14443A tag (e.g. MIFARE compatible) on the reader?
Yes of course, I placed a Mifare 1K Tag on both Touchatag. But just only one is called when the command "list" is executed. Did you already test with 2 readers on the same machine ?
When I connect the 2nd, the first is always used, when I disconnect the first, the second is used, but never in the same time.
PS : you can complete the hardware table for the chip of the touchatag.
Hi
When i run the list program, the application does not recognize touchatag reader connected to the USB.
The ACS 122 is detected and also the UID of the tag is listed.
Why is touchatag not recognized?
Hi sheetalv021,
When i run the list program, the application does not recognize touchatag reader connected to the USB.
The ACS 122 is detected and also the UID of the tag is listed.
Why is touchatag not recognized?
Your report is not clear, if list detected the ACS 122 and show UID, why do you say that touchatag is not recognized ?
--
Romuald
Hi rconty,
I have two readers, one from the ACS which is the ACR122U reader, and the other one from the Touchatag which make use of the acr122u hardware in their reader.
When I connect the touchatag reader and run the list program, the reader is not recognized.
Where as the ACR122U reader is recognized by the list program, which is obvious.
Since I want to write a standalone application for the ACR122U(also touchatag) reader to be able to communicate with the tags directly and also activate the tags to perform functions such as auto launch website etc, I expected the list to identify the touchatag reader too.
But touchatag reader is not being recognized.
I am new to C, and finding it difficult to code my application for the ACR122U. Is it possible to encode the actions to the tags using the libnfc?
Thank You
I have two readers, one from the ACS which is the ACR122U reader, and the other one from the Touchatag which make use of the acr122u hardware in their reader.
Could you send lsusb, pcsc_scan and list results when your Touchatag is plugged and one tag is present, please ?
Since I want to write a standalone application for the ACR122U(also touchatag) reader to be able to communicate with the tags directly and also activate the tags to perform functions such as auto launch website etc, I expected the list to identify the touchatag reader too.
If i understand correctly, you want to use Touchatag as "card" which communicate with the reader (ACR122U) ?
I am new to C, and finding it difficult to code my application for the ACR122U. Is it possible to encode the actions to the tags using the libnfc?
The library libnfc is a middle-level layer : it allow some hardware abstraction and provide a simple way to communicate using NFC specifications, but it doesn't provide, for now, API like : nfc_encode_action or nfc_decode_vcard (for example). At this time no data organisation or particular security layer is in libnfc.
You can manipulate NFC devices and put/get some data using libnfc but you need to "encode" your actions manually. Some manufacturers start to use RFID/NFC to do something like you want : store "action" in tags and play it when you put tag on reader but I don't know if there is some standard/specifications to do that.
--
Romuald
Hi Romauld
I get a message "Error connecting to reader" when i run list.exe with the toucatag reader connected.
I have not tested with lsusb and pcsc_scan.
I want to use the touchatag reader and tag for my project. Since the tags from toucatag are ISO14443 compatible, I can use it with the corresponding reader.
All that I am trying to do is to develop what touchatag has done, on my local machine, independent of registration.
I have been working simultaneously with the NFC 6131 nokia SDK, to develop my application for the OMNIKEY reader. I am waiting for the reader to arrive.
Meanwhile I found the libnfc api, and I was trying to see if I could use it for this project, or another project that I will start working on. Even with the java api for OMNIKEY, I am stuck on encoding the action into the tag. I am able to read/write from/into the tag, but not encode an action.
Please let me know the lsusb, and pcsc_scan, ----------???
Hi,
I get a message "Error connecting to reader" when i run list.exe with the toucatag reader connected.
I bought two touchatag and they works fine under Linux. I don't have any Windows OS access, so I can't say anything about it.
All that I am trying to do is to develop what touchatag has done, on my local machine, independent of registration.
Sounds good.
Please let me know the lsusb, and pcsc_scan
Sorry, theses commands are useful under POSIX system, like GNU/Linux, etc.
I don't know how to debug readers under Windows, sorry.
--
Romuald
Hi Romuald,
I have developed the initial stage of my application, by making use of the ACR122 Reader API in Java. This is a standalone application. It works well with the ACR 122 and Omnikey 5121 and 5321 readers. I have got 3 readers working with my application now. So not worried about Touchatag for the time being.
Will keep you posted on my next Project.
Thank you.
Just to mention it: I ordered a touchatag some two weeks back, and although looking very much like the ones posted on the hardware compatibility list, it returns a USB identifier of 072F 90CC. Seems they use an ACR38 device now (although in the case of the old ACR122). The libnfc however seems to work anyways (as far as I have tested)...
Edit: I have attached a couple of photos...
Last edited by honst (2009-10-10 16:06:21)
Just to mention it: I ordered a touchatag some two weeks back, and although looking very much like the ones posted on the hardware compatibility list, it returns a USB identifier of 072F 90CC. Seems they use an ACR38 device now (although in the case of the old ACR122). The libnfc however seems to work anyways (as far as I have tested)...
First of all, thank you very much for these excellent quality pictures. If you do not mind I would like to replace the ACR122 picture on the (main)website with yours, since the chips are much more visible on your photos.
Secondly, this is a problem the ACS ACR122U(10x) reader (old firmware) camps with from the start. It has the same Vendor/Device ID as the ACR38. Therefor it was immediately compatible with the active pcsc-lite package for linux. But of course, it stays a different reader with different features. The "inserted-card-emulation" which they use is a work-around is quite innovative and seems to work fine, at least if you use it the way like libnfc does. They introduced with their new firmware ACR122U20x a new way of communicating (which has an own new Vendor/DevId). But this new firmware seems to contain until today several bugs, official support for most of the sold new ACR122U readers (<206) are dropped by pcsc-lite. My advice still is to by an old ACR12210x version (the touchatag one), or wait for a reasonable new version which is tested for all platforms. ACS currently offered me to send a ACR122T (small version), to test compatibility with libnfc, but I have not received it yet. It is sad the firmware on their devices could not be upgraded, this would have solved a lot of problems "remotely".
Thanks again for the photos, I hope this store makes more sense for those wondering why this reader identifies itself different sometimes.
Sure, feel free to use the pic on the main site.
And thanks for your explanations...
Andreas
Hey Andreas,
I have updated your image with the corresponding "test-pins" which are connected to the PN532 chip.
For development it could be useful to use the ACR122 assembly and a microcontroller development board.
The "Error connecting to reader" was one I got really pissed off about.
And then I remembered how I fixed it before.
In the file /etc/libccid_Info.plist
Find <key>ifdDriverOptions<key>
And underneath change the string to 0x0005
It has to do with some bogus firmware thing.
Then it should work.
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 2 official extensions. Copyright © 2003–2009 PunBB.