Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

status event should contain the card ATR #2

Closed
santigimeno opened this issue Jul 5, 2013 · 5 comments
Closed

status event should contain the card ATR #2

santigimeno opened this issue Jul 5, 2013 · 5 comments

Comments

@santigimeno
Copy link
Owner

As reported in:

jokesterfr/node-pcsc#10 (comment)

by @jokesterfr

@santigimeno
Copy link
Owner Author

santigimeno added a commit that referenced this issue Jul 5, 2013
- Of the inserted card.
- Refactoring of the code that creates a Buffer instance into a
  separate function.
- Update the example and README
- It fixes bug #2
@santigimeno
Copy link
Owner Author

@jokesterfr, can you test with master that the ATR of the card is retrieved with the status event?

Regarding the issue with multiple card readers, I'm testing with 2 readers using the example/example.js application, plugging / unplugging them and they're both detected correctly. What do you see?

@jokesterfr
Copy link

@santigimeno the card readers at the office are internal, so I cannot plug them in/out easily. I will give it a new try on monday (my colleague updated some drivers, it may be not related to node-pcsclite nor pcsclite).

I'm gonna test the ATR status event this evening at home, thanks !

@jokesterfr
Copy link

I can get the ATR with Master, wonderful =)
Nevertheless it seems that the callback of reader.connect(callback); is never called (I never see the output of console.log('Protocol...').
I tought this section should go with console.log("card inserted"), what do you think about it?

@santigimeno
Copy link
Owner Author

You're right, for the example would make more sense. Also reader.disconnect should be called when we detect the card has been removed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants