ankitdaf / ismb-snep-java Goto Github PK

I want to send max data > 256 byte  from acr to andriond htc . .How do I do use 
snep ..



Please provide any additional information below.

What steps will reproduce the problem?
1. Import project to Eclipse (and follow instructions about error display)
2. Run as ... Java Application

What is the expected output? What do you see instead?
Expected: Something like "Connection established"

Instead:
Get factory
Get terminals
Terminal name: ACS ACR122 0
Exception in thread "Timer-0" java.lang.NullPointerException
    at it.ismb.snep.SenderToPhone$ThreadSender.run(SenderToPhone.java:104)
    at it.ismb.snep.SenderToPhone$InitiatorTask.run(SenderToPhone.java:73)
    at java.util.TimerThread.mainLoop(Unknown Source)
    at java.util.TimerThread.run(Unknown Source)
Device not supported, only ACS ACR122 is supported now

What version of the product are you using? On what operating system?
Latest version.
OS: Win7 x64

Please provide any additional information below.
No specific information available, I think. We are using the ACS ACR-122U-A9 
device (and a Galaxy S with CM10).

What steps will reproduce the problem?
1.when I connect acr122s , I use usb-to-serial drivers .It can connect success 
using acr122s' sdk.
2. But this project cant run,the console shows:
3. Get factory
   Get terminals
   There are not terminals.
   invalid card terminal
   Exception in thread "Timer-0" java.lang.NullPointerException
    at it.ismb.npp.SenderToPhone$ThreadSender.run(SenderToPhone.java:109)
    at it.ismb.npp.SenderToPhone$InitiatorTask.run(SenderToPhone.java:77)
    at java.util.TimerThread.mainLoop(Unknown Source)
    at java.util.TimerThread.run(Unknown Source)

Is acr122s belong to acr122 series?It's the problem of the reader version or 
the usb2serial driver?Since acr122 is hard to buy,how about acr122u ?Thanks!

What steps will reproduce the problem?
1. With ACR122 NFC Reader connected, launch NdefReaderDemo 
2. I don't have Nexus S or tag near the reader

What is the expected output? What do you see instead?
Exception in thread "Timer-0" java.lang.ArrayIndexOutOfBoundsException
instead of Tag reading ... 

What version of the product are you using? On what operating system?
- ACR122 NFC Reader driver 1.1.6.3
- Windows 7 x64

Please provide any additional information below.
The error code is : 0x63 0x00

Debug output : 
Get factory
Get terminals
Terminal name: ACS ACR122 0
card: PC/SC card in ACS ACR122 0, protocol T=0, state OK
Protocol:T=0
Called Procedure to Receive data .. INITIATOR MODE
[DEBUG] {sending   [23 bytes]} 0xFF 0x00 0x00 0x00 0x12 0xD4 0x56 0x01 0x02 
0x04 0x46 0x66 0x6D 0x01 0x01 0x10 0x03 0x02 0x00 0x01 0x04 0x01 0x96 
[DEBUG] {receiving [2 bytes]} 0x63 0x00 
[DEBUG] {sending   [8 bytes]} 0xFF 0x00 0x00 0x00 0x03 0xD4 0x52 0x01 
[DEBUG] {receiving [2 bytes]} 0x63 0x00 
Exception in thread "Timer-0" java.lang.ArrayIndexOutOfBoundsException
       at fr.mycompany.nfc.Util.appendToByteArray(Util.java:98)
       at fr.mycompany.nfc.Util.subByteArray(Util.java:119)
       at fr.mycompany.nfc.IsmbSnepConnection.transceive(IsmbSnepConnection.java:140)
       at fr.mycompany.nfc.IsmbSnepConnection.close(IsmbSnepConnection.java:88)
       at fr.mycompany.nfc.PhoneToSender$ThreadSender.run(PhoneToSender.java:107)
       at fr.mycompany.nfc.PhoneToSender$InitiatorTask.run(PhoneToSender.java:74)
       at java.util.TimerThread.mainLoop(Timer.java:555)
       at java.util.TimerThread.run(Timer.java:505)

What steps will reproduce the problem?
1. Run the ReaderToPhone Code.
2. Place the phone up against the reader when ready.
3. The message is not sent.

What is the expected output? What do you see instead?
Instead of send the message, I see that output:
IN JUMP FOR DEP done..
[DEBUG] {sending   [10 bytes]} 0xFF 0x00 0x00 0x00 0x05 0xD4 0x40 0x01 0x11 
0x20 
[DEBUG] {receiving [7 bytes]} 0xD5 0x41 0x00 0x00 0x00 0x90 0x00 
3 
[DEBUG] {sending   [10 bytes]} 0xFF 0x00 0x00 0x00 0x05 0xD4 0x40 0x01 0x11 
0x20 
[DEBUG] {receiving [7 bytes]} 0xD5 0x41 0x00 0x00 0x00 0x90 0x00 
3 
[DEBUG] {sending   [10 bytes]} 0xFF 0x00 0x00 0x00 0x05 0xD4 0x40 0x01 0x11 
0x20 
[DEBUG] {receiving [7 bytes]} 0xD5 0x41 0x00 0x00 0x00 0x90 0x00 
3 
[DEBUG] {sending   [10 bytes]} 0xFF 0x00 0x00 0x00 0x05 0xD4 0x40 0x01 0x11 
0x20 
[DEBUG] {receiving [7 bytes]} 0xD5 0x41 0x00 0x00 0x00 0x90 0x00 
3 
[DEBUG] {sending   [10 bytes]} 0xFF 0x00 0x00 0x00 0x05 0xD4 0x40 0x01 0x11 
0x20 
[DEBUG] {receiving [5 bytes]} 0xD5 0x41 0x13 0x90 0x00 
1

What version of the product are you using? On what operating system?
Last version, Windows 7 and Nexus S with Android 4.1.2.

Please provide any additional information below.
I have a lot of questions about the code. I suppose that after "IN JUMP FOR 
DEP" we wait till the length of the reply is 7, what means that the phone is 
waiting the data. However, I receive the repplies you can see above.

Could you help me? Could it be because the phone sends that message while the 
thread is sleeping?

I have done the tests with Android Beam enabled and disabled with no 
differences.

I would be grateful if you could help me.