Is anyone doing HK Octopus card development? For Octopus follows the FeLiCa standard, and it has a public card mfgID that we can read. However the Octopus card has a 9-digit UID printed on it, and I'm hoping to read that number from the card using NFC card reader.
Related
I want to develop my driver based on this Microsoft base code: https://github.com/Microsoft/Windows-driver-samples/tree/master/audio/sysvad
My idea is:
(1) when user says to computer: robert, what is weather today?
(2) Then the voice is captured by mic array driver A and send to my application.
(3) My application will change the voice to: Alexa, what is weather today. And send it to a virtual driver.
(4) The virtual driver captures the voice and send it to Alexa application.
(5) Alexa responses.
Is it possible?
I think so,
you will need to also develop your own digital assistant using bot framework
also in your driver, you will need to support MVA
Im having a problem with switching a Mifare Plus SE from SL1 to SL3, using acs acr122U with pn532
In SL1 the card is detected as a Mifare Classic (Same ATR) and to perform the switch i need to activate the comunication in 14443-4 and do the auth command with the SL3 switch key. I trying to activate the comunication in 14443-4, but im not finding how.
In other card which its already in SL3 (Also on SL1) the card is activated without problems in 14443-4 and i can send the mifare plus operations without problems.
Im using Smartcardio and transmitcontrolcommand to send the commands to the acr122U trying to use these commands from the PN532 :
-inAutoPoll (Which detects the card as 10 (mifare card, not 14443-4 card)
-InListPassiveTarget (Actives the card as mifare classic too)
-inATR (Which ends with a timeout)
I tryed to inRelease and reactivate again, is not working neither.
Thanks for your time
The problem you are facing is MFP in SL1 acts as a MFC, and does not advertise support for 14443-4 in its SAK. Most high-level libraries will simply not try to send RATS to switch to -4.
For MFP authentication command to work on 0x9001 (prerequisite for switching to SL3), you actually have to be in -4 mode, so you'll have to force sending RATS to get to -4, even if not advertised by card. Depending on your NFC library's API, this may not be possible.
For implementation in backend-agnostic code, I ended-up reimplementing -4 framing and using low-level communication APIs just for this case.
Once in SL3, -4 support is advertised, and switching happens transparently in most communication libraries.
I'm making an android NFC app using Mifare Classic tags. This app is working good.
However, not all Android device have a NXP NFC chip, some have a Broadcom NFC chip which does not support Mifare Classic tag.
So, for this kind of device I'm trying to use the NXP NTag213 or NTag216 tag which are supported by Broadcom NFC chip.
I used the "NXP TagInfo" app to try to read this kind of tag and in the techList the tag is known as [MifareUltralight-NfcA-Ndef-NdefFormatable].
I had a look on NXP datasheet and it stated that you can write data on NTag21X with Ndef format.
I can get an Ndef instance from my NTag but when I try to write my NdefMessage, everytime I get an IOException when I try to get the connexion by ndef.connect().
Do you have any idea why ?
When I insert a Smart Card to the reader after receiving ATR I can see in the driver log a number of IOCTL's that are not sent by my application (as is not running).
My question is if there is any document, describing Smard Card communication establishment in windows?
There is the Win32 API for communicating with smart cards within Windows
platform in form SCardXXX. Similar implementation for Linux is developed under
Muscle project as PC/SC Lite API.On Windows platform Following functions will be used:
SCardEstablishContext
SCardListReaders
SCardConnect
SCardReconnect
SCardDisconnect
SCardReleaseContext
SCardTransmit
Figure shows that how the smart card intract with application on windows platform.
For more information see the Here
pn532 card emulation mode
I want to konw pn532 card emultion . I success running "iso 14443-4A emulation mode" but it have not block data like mifare card . How can i make block data ? what frame is run "mifare classic card mode" . And in virtual card mode in samconfiguration , how can i get sam ( secure access module)?.
I have arduino mega adk , and nfc shield v1.0 ( pn532) . In this situation , how can i connect "sam" to nfc shield (pn532 )? . please help me .
I believe that if configured properly the PN532 can perform card emulation with a smart card that is compatible with SWP/HCI protocol (single wire connection, ETSI TS 102 603, 102 622).
If you can get a sample test card that supports this protocol, and for which you know the keys, then you could do APDU (ISO 14443-4) card emulation.
You can use PN532 as a NFC tag 4 card which can contain a NDEF message (block data?). If you use Arduino, https://github.com/Seeed-Studio/PN532 is for you.