nfcpy

PHDC agent with Android

Asked by EPx

I am using the PHDC agent script, that depends on card emulation to work.

In short, the trunk version does not work (error: Check NDEF Failed - status = 146, regardless of reader app) but the version in branch dev-emulate-tag (which seems to be older) works, I could exchange IEEE 11073 packets using my app.

Is this expected, that is, the dev-emulate-tag more advanced in terms of tag emulation?

Question information

Language:
English Edit question
Status:
Solved
For:
nfcpy Edit question
Assignee:
No assignee Edit question
Solved by:
Stephen Tiedemann
Solved:
Last query:
Last reply:
Revision history for this message
Stephen Tiedemann (stephen-tiedemann) said : 		#1

The trunk version is currently the most advanced. The PHDC implementation
in trunk is for the adopted V 1.0 and I guess the one you're using was for
the Candidate Spec. There are differences in the NDEF layout, please verify
with your implementation.

Revision history for this message
EPx (elvis-pfutzenreuter) said : 		#2

I will check the differences in PHDC. The problem seems to be in
a level below, in tag emulation, since the Android does not recognize
the NDEF in tag at all.

On Aug 1, 2013, at 5:31 PM, Stephen Tiedemann wrote:

> Your question #233165 on nfcpy changed:
> https://answers.launchpad.net/nfcpy/+question/233165
>
> Status: Open => Answered
>
> Stephen Tiedemann proposed the following answer:
> The trunk version is currently the most advanced. The PHDC implementation
> in trunk is for the adopted V 1.0 and I guess the one you're using was for
> the Candidate Spec. There are differences in the NDEF layout, please verify
> with your implementation.
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
> https://answers.launchpad.net/nfcpy/+question/233165/+confirm?answer_id=0
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.launchpad.net/nfcpy/+question/233165
>
> You received this question notification because you asked the question.

Revision history for this message
Best Stephen Tiedemann (stephen-tiedemann) said : 		#3

You can check with "examples/tagtool.py emulate tt3" if there is a general
problem or not. With "examples/ndeftool.py make smartposter ..." you can
create an NDEF to serve with tagtool, see the documentation for more
options.

Revision history for this message
EPx (elvis-pfutzenreuter) said : 		#4

The problem was simply that I was failing to pass the test number (e.g. "-t 1") to the script (in emu branch, it defaults to 1).

I followed how tagtool worked (its emulation worked) and found that no NDEF read/write callbacks were being implemented, then found that no test method was being called.