×

Discussion Board

Results 1 to 8 of 8
  1. #1
    Registered User
    Join Date
    Sep 2006
    Posts
    10

    Problem using PushRegistry on Mifare tags

    Hi,

    I have a set of RFID Mifare 1k Tags and a Nokia 6131 NFC v3.12.

    I am writing a test MIDlet to verify that Tag detection works.

    So far I have been able to register a TargetListener on a RFID_TAG and this works great:

    DiscoveryManager.getInstance().addTargetListener(this,
    TargetType.RFID_TAG);

    On the other hand, I am trying to register a PushRegsitry entry, either statically via the JAD file or Dynamically via the PushRegistry API and none of these work when I present the phone to the TAG.

    The code registering the TAG detection in my MIDlet is:

    PushRegistry
    .registerConnection("ndef:rtd?name=urn:nfc:wkt:RFID_TAG",
    "test.NFCMidlet", "nfc:ndef;type=mf1k;uid=*");

    Even by replacing "nfc:ndef;type=mf1k;uid=*" with "*", it does not work. The phone does not complain during PushRegistry connection registration but does not do anything when I quit the application and present the device to the TAG.

    I have gone through some examples and various threads in this forum, but neither helped.

    Thanks for any help

    Olivier

  2. #2
    Regular Contributor
    Join Date
    Jul 2007
    Location
    Lisbon - Portugal
    Posts
    96

    Re: Problem using PushRegistry on Mifare tags

    What kind of data does the tag contain?
    With the URLs you specified, the midlet will autostart ONLY if the data contained in the Mifare is formatted with NFC Forum NDEF Record format.

    You can try this, instead:

    nfc:undefined_format;type=mf1k;uid=*

    Please refer to this thread:
    http://discussion.forum.nokia.com/fo...d.php?t=107998

    Most of the common problems were addressed there.
    Additionally, you may want to check the JSR-257 spec in depth:
    http://jcp.org/aboutJava/communitypr...257/index.html

  3. #3
    Registered User
    Join Date
    Sep 2006
    Posts
    10

    Re: Problem using PushRegistry on Mifare tags

    Thanks for the prompt response.

    However, in the targetDetected method, the following happens when I present the phone with the open MIDlet to a TAG:

    The TargetType is RFID_TAG

    The getURL on the TargetProperties entry returns in the MIDLET the following:

    nfc:ndef;type=mf1k;uid=XXXXX

    In any case, I have tried your suggestion but that did not do the trick to autostart the application when presented to the TAG.

    For information, I have used the Write to Tag embedded application to write a Link.

    What is unclear to me is the following:

    ndef:rtd?name=urn:nfc:wkt:RFID_TAG

    Everything up to wtk: is defined in the NFC Forum specifications, the rest is unclear to me. I have seen some posts with Sp, S, U....

    Are you also aware of any related bug related to the PushRegistry and the TAG detection in my software version: 3.12 (USA)?

    Olivier

  4. #4
    Regular Contributor
    Join Date
    Jul 2007
    Location
    Lisbon - Portugal
    Posts
    96

    Re: Problem using PushRegistry on Mifare tags

    Ok, undefinedformat should not work, because you wrote NFC Forum data on the tag.

    Btw, how were you able to write the Link to the mifare 1k tag?
    I have a set of blank mf1k tags end the phone says that it can't write to those tags. However, with Topaz tags, it works fine.

    "Everything up to wtk: is defined in the NFC Forum specifications, the rest is unclear to me. I have seen some posts with Sp, S, U..."

    They are specified in the NFC Forum Specs:
    Sp -> Smart Poster [NFCForum-SmartPoster_RTD_1.0.pdf]
    T -> Text [NFCForum-TS-RTD_Text_1.0.pdf]
    U -> URI [NFCForum-TS-RTD_URI_1.0.pdf]

    S -> Haven't found info on this one

    For example, with an empty mf1k tag, I use this:
    In the JAD:
    MIDlet-Permissions: javax.microedition.io.PushRegistry
    MIDlet-Push-1: nfc:undefined_format,TargetDetectorMidlet,nfc:rf;type=mf1k;uid=*

    or using the PushRegistry API:

    String pushEntry = "nfc:undefined_format";
    String filter = "nfc:rf;type=mf1k;uid=*";

    if (!registered)
    {
    PushRegistry.registerConnection(pushEntry, this.getClass().getName(), filter);
    }


    This is tested with the real device and works.

    I am not aware of any bug related to that specific parts in that SW version.
    Recently, I have updated the phone to 5.11, but I made this tests before the update, with the version 3.12.

    Good Luck

  5. #5
    Registered User
    Join Date
    Sep 2006
    Posts
    10

    Re: Problem using PushRegistry on Mifare tags

    Thanks for the info. Will try this out.
    For info, I was able to write to the tags using the embedded write to tag application under the NFC folder. As simple as that ;-)
    I will let you know how test goes.

    Olivier

  6. #6
    Registered User
    Join Date
    Sep 2006
    Posts
    10

    Re: Problem using PushRegistry on Mifare tags

    Was still unable to launch the application when presenting the device to the tag.
    I have also tried "Sp" and get an exception when at PushRegistry registration...
    As my application reacts to RFID_TAG type, would it make sense to do the following:

    PushRegistry
    .registerConnection("ndef:rtd?name=urn:nfc:wkt:RFID_TAG",
    "test.NFCMidlet", "nfc:ndef;type=mf1k;uid=*");

    I have also the following:

    DiscoveryManager.getInstance().addTargetListener(this,
    TargetType.RFID_TAG);
    DiscoveryManager.getInstance().addTransactionListener(this);

    In the NFC section, I have turned off Tag Detection. (If on, the OS captured the Tag that point to a URL and prompts me to launch the browser).
    I have configured the Tag using the Transmit to Tag application and create a Bookmark.

    I have also tried this on a newer phone, 5.11, still with the same results...

    Olivier

  7. #7
    Regular Contributor
    Join Date
    Jul 2007
    Location
    Lisbon - Portugal
    Posts
    96

    Re: Problem using PushRegistry on Mifare tags

    Well if you disable tag detection, the Push Registry Activation will not work. When you disable the tag detection, I'm almost sure that the RF Hardware is disconnected. This is useful if you wish to save battery, for example, or if you just don't want the phone to be sensitive to RF Tags.

    When you say:
    "(If on, the OS captured the Tag that point to a URL and prompts me to launch the browser)", I think that if the PushRegistry entry is ok, it will override the default OS applications.

    I cannot test this behavior because I cannot write to an empty ordinary Mifare 1k tag using the default "write to tag" application.

    Good Luck

  8. #8
    Registered User
    Join Date
    Sep 2006
    Posts
    10

    Re: Problem using PushRegistry on Mifare tags

    I have tested the application on empty RFID tags and the PushRegistry works fine for the nfc:undefined_format.
    I guess that the write to tag application embedded with the 6131 may only work with the on-board applications as I have not been able to intercept any of these tags using the Push Registry. It may also mean that the embedded 6131 application has precedence over the push registry for any tags that have been written with the "write to tag" application.
    This is fine as I will write my own process to write tags.

Similar Threads

  1. netcards - Problem with opening adapter
    By kernj in forum Symbian Tools & SDKs
    Replies: 5
    Last Post: 2007-01-10, 08:56
  2. PushRegistry on reboot problem
    By jryanmyint in forum Mobile Java General
    Replies: 0
    Last Post: 2005-03-17, 20:53
  3. Problem: S60 SDK for CW in PC with .NET
    By anttij in forum Carbide.c++ IDE and plug-ins (Closed)
    Replies: 1
    Last Post: 2005-02-28, 11:36
  4. 7210 Silent Problem
    By MarkMckim in forum Mobile Java General
    Replies: 1
    Last Post: 2003-03-18, 12:36
  5. PJava runtime problem within Nokia 9210, Hrlp~!
    By Nokia_Archive in forum PersonalJava
    Replies: 1
    Last Post: 2002-05-28, 13:15

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
×