Hi Arnoud, I think you are doing everything right. I'm also working on a LLCP stack in java and noticed the same problem as described above. I don't have a solution right now except to send several CONNECT messages. Maybe the service layer needs some time to get initialized and that's the reason for the delay.
If you have a ACR122 nfc desktop reader you can try my LLCP stack in your browser with the NDEF Applet: www.grundid.de/nfc/ Regards, Adrian. On 4 Jan., 11:36, Arnoud van de Haar <[email protected]> wrote: > I have a Nexus S wich is running ICS 4.0.3 and want to communicate > with a NFC doorlocker. In the doorlocker we implemented the NFCIP-1 > layer and LLCP layer. > > I have done some tests communicating through the NPP service and have > a question about the reply I get from the Nexus S when I do a > connection request (LLCP). > > I send the following LLCP message for connecting: > 0x05, 0x22, 0x05, 0x01, 0x04, 0x06, 0x0F, 0x63, 0x6F, 0x6D, 0x2E, > 0x61, 0x6E, 0x64, 0x72, 0x6F, 0x69, 0x64, 0x2E, 0x6E, 0x70, 0x70 > > The reply I get from the Nexus S is: > 0x00 0x00 > > This seems to be an SYMM message, but I would expect to get a CC LLCP > message like: > 0x89 0x90 0x02 0x02 0x00 0x78 > > If I ignore the SYMM and send my NPP push message over LLCP, I'll get > the CC reply which I would expect to get earlier. after This I have to > send a SYMM package to get the reply (RR) for the NPP message. > > Can you tell me why I get a SYMM message reply on a CONNECT message > and how to get the CC message form the phone before sending the NPP > package? > > Regards, > Arnoud -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
