×

Discussion Board

Page 9 of 12 FirstFirst 123456789101112 LastLast
Results 121 to 135 of 177
  1. #121
    Registered User
    Join Date
    Oct 2006
    Location
    Berlin
    Posts
    201

    Re: 6131 NFC autostart on tag touch

    Quote Originally Posted by sdny View Post
    Hi, ok...it still wont work...this is what i used from the info i got from TagTestMIDlet:
    String pushEntry = "ndef:rtd?name=nokia.com:li:id"; (id tags)

    and

    String pushEntry = "ndef:rtd?name=nokia.com:li: op"; (operational tags)

    However, the TagTestMIDlet autolaunch does not work either.
    PushRegistryImpl::registerConnectionInternal registering connection: ndef:rtd?name=urn:nfc:wkt:U
    PushRegistryImpl: URL prefix='ndef'
    PushRegistryImpl: Found handler for prefix.

    Registry check only prefix='ndef' and not more with :......
    :..... = registry no check this

  2. #122
    Registered User
    Join Date
    Jul 2007
    Posts
    29

    Re: 6131 NFC autostart on tag touch

    Quote Originally Posted by Raluca_ View Post
    @sdny

    My question was not related to the type of tags (Jewel, MiFare etc.) but to the data on the tags.

    The urls you mentioned - String pushEntry = "ndef:rtd?name=nokia.com:li:id"; (id tags) and String pushEntry = "ndef:rtd?name=nokia.com:li: op"; (operational tags) - will only work if the data on your tags is NDEF formatted data, and the record type for the NDEF data is "nokia.com:li:id" and "nokia.com:li: op".

    If these are in fact tags that contain NTIP data, you have to change your Push Registry entry accordingly.

    Can you please try the following:

    1. Run the TagTestMIDlet.
    2. Choose "Read NDEF" and touch one of the tags that you want to use later for launching your MIDlet.
    3. Let me know what the MIDlet displays for your tag. Tag Type and Tag UID are not important, the rest of the information is. You could get a "No NDEF message on target" message or information about the NDEF record: type, format. Please let me know your results.
    1st tag:
    Tag Type:simpletag
    UID:04xxxxxxxxxxxx
    No NDEF Message on target

    2nd tag:
    Tag type:jewel
    Tag UID:07xxxxxxxxxxx
    Record type: nokia.com:li:id
    Record Format: 4
    Record payload: EF0000034C7464

  3. #123
    Regular Contributor
    Join Date
    Mar 2007
    Location
    Helsinki, Finland
    Posts
    91

    Re: 6131 NFC autostart on tag touch

    Quote Originally Posted by sdny View Post
    1st tag:
    Tag Type:simpletag
    UID:04xxxxxxxxxxxx
    No NDEF Message on target

    2nd tag:
    Tag type:jewel
    Tag UID:07xxxxxxxxxxx
    Record type: nokia.com:li:id
    Record Format: 4
    Record payload: EF0000034C7464
    So, the first tag contains no NDEF data, it is probably an NTIP tag and we'll discuss that later.

    The second tag contains NDEF data, so you should be able to launch your MIDlet using it if you use a different Push Registry Connection url.

    Can you try registering the following in your MIDlet, compile, run it on the phone once and then try to launch it with the second tag?

    String pushEntry = "ndef:external_rtd?name=nokia.com:li:id";

    Please let me know how it goes.
    Raluca Cindrea
    Helsinki, Finland
    www.nokia.com/nfc

  4. #124
    Registered User
    Join Date
    Jul 2007
    Posts
    29

    Re: 6131 NFC autostart on tag touch

    "Unknown Service Type"

  5. #125
    Regular Contributor
    Join Date
    Mar 2007
    Location
    Helsinki, Finland
    Posts
    91

    Re: 6131 NFC autostart on tag touch

    Quote Originally Posted by sdny View Post
    "Unknown Service Type"
    Are you using any filters? And are you using the TagTestMIDlet or a different MIDlet?
    Raluca Cindrea
    Helsinki, Finland
    www.nokia.com/nfc

  6. #126
    Registered User
    Join Date
    Jul 2007
    Posts
    29

    Re: 6131 NFC autostart on tag touch

    Quote Originally Posted by Raluca_ View Post
    Are you using any filters? And are you using the TagTestMIDlet or a different MIDlet?
    Thats wat happened with my own MIDlet....

    this is what I get with TagTestMidlet:
    Error when puchregistering Invalid Parameter

  7. #127
    Registered User
    Join Date
    Oct 2006
    Location
    Berlin
    Posts
    201

    Re: 6131 NFC autostart on tag touch

    'Unknown Service Type' - TAG with no Entry and no service type after production.
    Read UID from TAG with active Midlet = no problem.
    autolaunch with .jad entry for this TAG type?

    As is the correct entry for jad. If there are one.
    My last question in this Thread.

  8. #128
    Registered User
    Join Date
    Oct 2006
    Location
    Berlin
    Posts
    201

    Re: 6131 NFC autostart on tag touch

    Example:
    Code:
    try
    		{
    			PushRegistry.registerConnection("ndef:","mobileServer","*");
    		}
    		catch (ClassNotFoundException e)
    		{
    			e.printStackTrace();
    		}
    		catch (IOException e)
    		{
    			e.printStackTrace();
    		}
    Emulator command: C:\Nokia\Devices\Nokia_6131_NFC_SDK_1_0\bin\midp.exe -Xdescriptor.............
    PushRegistryImpl::registerConnectionInternal registering connection: ndef:
    PushRegistryImpl: URL prefix='ndef'
    PushRegistryImpl: Found handler for prefix.

    PushRegistry check 'ndef:' and not more!!!

    ndef:blabla = ok hahaha. NOT GOOD with Registry
    Sorry only SDK Emulator.

  9. #129
    Regular Contributor
    Join Date
    Mar 2007
    Location
    Helsinki, Finland
    Posts
    91

    Re: 6131 NFC autostart on tag touch

    As you could read in the Release Notes:

    " PushRegistry calls on emulator now do not throw
    an exception for "ndef:" and "secure-element:"
    protocols, but callbacks are never executed."
    Raluca Cindrea
    Helsinki, Finland
    www.nokia.com/nfc

  10. #130
    Registered User
    Join Date
    Oct 2006
    Location
    Berlin
    Posts
    201

    Re: 6131 NFC autostart on tag touch

    Quote Originally Posted by Raluca_ View Post
    So, the first tag contains no NDEF data, it is probably an NTIP tag and we'll discuss that later.

    The second tag contains NDEF data, so you should be able to launch your MIDlet using it if you use a different Push Registry Connection url.

    Can you try registering the following in your MIDlet, compile, run it on the phone once and then try to launch it with the second tag?

    String pushEntry = "ndef:external_rtd?name=nokia.com:li:id";

    Please let me know how it goes.
    http://forum.nokia.com/main/resources/technologies/nfc/

    Supports most popular tag formats for read and write: Mifare 1K, 4K, and Ultralight; Topaz; Jewel (read-only); and FeliCa (non-secure).
    Contains secure element: Global Platform 2.1.1-compliant Java smart card, supporting card emulation for ISO 14443 Type A and Mifare 4K cards.
    Supports JSR-257 for accessing NFC features from third-party applications.

  11. #131
    Registered User
    Join Date
    Oct 2006
    Location
    Berlin
    Posts
    201

    Re: 6131 NFC autostart on tag touch

    Quote Originally Posted by Raluca_ View Post
    As you could read in the Release Notes:

    " PushRegistry calls on emulator now do not throw
    an exception for "ndef:" and "secure-element:"
    protocols, but callbacks are never executed."
    Sorry, but if a SDK cannot do that. Which is then for a SDK. Not against you Raluca _ personally.

  12. #132
    Registered User
    Join Date
    Oct 2006
    Location
    Berlin
    Posts
    201

    Re: 6131 NFC autostart on tag touch

    Example 2 (with C:\Nokia\Devices\JSR_257_RI_1_0\Prototype_3_0_S40_128x128_MIDP_Emulator\bin\emulator.exe)

    Code:
    try
    		{
    			PushRegistry.registerConnection("ndef:rtd?name=","mobileServer","*");
    		}
    		catch (ClassNotFoundException e)
    		{
    			e.printStackTrace();
    		}
    		catch (IOException e)
    		{
    			e.printStackTrace();
    		}
    Emulator command: C:\Nokia\Devices\JSR_257_RI_1_0\Prototype_3_0_S40_128x128_MIDP_Emulator\bin\midp.exe -Xdescriptor...................
    PushRegistryImpl::registerConnectionInternal registering connection: ndef:rtd?name=
    PushRegistryImpl: URL prefix='ndef'
    PushRegistryImpl: Found handler for prefix.
    startApp threw an Exception
    java.lang.IllegalArgumentException: Record name has illegal format: 'urn:nfc:wkt:'

    This SDK check more elements from the ConnectionString!
    This help more for all with no realdevice!

  13. #133
    Registered User
    Join Date
    Jul 2007
    Posts
    29

    Re: 6131 NFC autostart on tag touch

    So what do i do about NTIP tags?

  14. #134
    Registered User
    Join Date
    Oct 2006
    Location
    Berlin
    Posts
    201

    Re: 6131 NFC autostart on tag touch

    The next attempt with Prototype_3_0_S40_128x128_MIDP_Emulator\bin\midp.exe?

    Code:
    try
    		{
    			PushRegistry.registerConnection("ndef:external_rtd?name=","mobileServer","*");
    		}
    		catch (ClassNotFoundException e)
    		{
    			e.printStackTrace();
    		}
    		catch (IOException e)
    		{
    			e.printStackTrace();
    		}
    PushRegistryImpl::registerConnectionInternal registering connection: ndef:external_rtd?name=
    PushRegistryImpl: URL prefix='ndef'
    PushRegistryImpl: Found handler for prefix.
    startApp threw an Exception
    java.lang.IllegalArgumentException: The record type name must begin with 'urn:nfc:ext:'

    URI Identifier Code

    0 0x00 N/A. No prepending is done, and the URI field contains the unabridged URI.
    1 0x01 http://www.
    2 0x02 https://www.
    3 0x03 http://
    4 0x04 https://
    5 0x05 tel:
    6 0x06 mailto:
    7 0x07 ftp://anonymous:anonymous@
    8 0x08 ftp://ftp.
    9 0x09 ftps://
    10 0x0A sftp://
    11 0x0B smb://
    12 0x0C nfs://
    13 0x0D ftp://
    14 0x0E dav://
    15 0x0F news:
    16 0x10 telnet://
    17 0x11 imap:
    18 0x12 rtsp://
    19 0x13 urn:
    20 0x14 pop:
    21 0x15 sip:
    22 0x16 sips:
    23 0x17 tftp:
    24 0x18 btspp://
    25 0x19 btl2cap://
    26 0x1A btgoep://
    27 0x1B tcpobex://
    28 0x1C irdaobex://
    29 0x1D file://
    30 0x1E urn:epc:id:
    31 0x1F urn:epc:tag:
    32 0x20 urn:epcat:
    33 0x21 urn:epc:raw:
    34 0x22 urn:epc:
    35 0x23 urn:nfc:
    36…255 0x24..0xFF RFU

    See You http://www.eetchina.com/ARTICLES/200...URCES=DOWNLOAD
    Help?

    help for nfc_ext by directory
    file:///C:/Nokia/Devices/Nokia_6131_...ext/index.html
    to
    Interface JewelTagConnection
    for write and read data from Jewel....


    OR
    switch all to Nokia 6131 NFC SDK 1.1.
    More Help?!
    Note!
    Not SDK 1,0 and SDK 1.1
    only SDK 1.1 or SDK 1.0
    Last edited by mariosas; 2007-08-07 at 08:13.

  15. #135
    Registered User
    Join Date
    Oct 2006
    Location
    Berlin
    Posts
    201

    Re: 6131 NFC autostart on tag touch

    Quote Originally Posted by sdny View Post
    So what do i do about NTIP tags?
    1. Attempt
    In emulator
    =
    PushRegistryImpl::registerConnectionInternal registering connection: ndef:rtd?name=urn:nfc:ext:nokia.com:li:id
    PushRegistryImpl: URL prefix='ndef'
    PushRegistryImpl: Found handler for prefix.

    and in device
    =
    Illegall Argument java/lang/IllegalArgumentException with Invalid Parameter

    2. Attempt

    In emulator
    =
    PushRegistryImpl::registerConnectionInternal registering connection: ndef:external_rtd?name=nokia.com:li:id
    PushRegistryImpl: URL prefix='ndef'
    PushRegistryImpl: Found handler for prefix.

    and in device
    =
    Illegall Argument java/lang/IllegalArgumentException with Invalid Parameter

    !!!Result: The SDK 1.1 is not also suitable for it!!!

    in the dok.
    -
    2.2 NFC Forum External Type
    The External Type Name is meant for organizations that wish to self-allocate a name space to be
    used for their own purposes.
    An External Type is identified in an NDEF record by setting the TNF field value to 0x04, as
    defined in the NDEF specification [NDEF].
    The External Type is, much like a Well Known Type, an URN, with the NID of “nfc”. However,
    the NSS specific part is put into another namespace named “ext”. A canonical version of the
    External Type Name would look like:
    “urn:nfc:ext:example.com:f”
    The External Type Name MUST be formed by taking the domain name of the issuing
    organization, adding a colon, and then adding the type name as managed by the organization.
    As with Well Known Types, the binary encoding of External Type Name inside NDEF messages
    MUST omit the NID and the NSS prefix of “ext”.
    NFC
    4.2 Unknown Record Types
    Applications MUST ignore records which have a Well Known Type or an External Type that
    they do not recognize.
    -

    example with http://wiki.forum.nokia.com/index.ph...gistry_example
    Result: Push ok and midlet autolaunch???

    Mhm!
    with entry
    ndef:external_rtd?name=urn:nfc:ext:nokia.com:id","mobileServer","*"
    push ok
    with entry
    ndef:external_rtd?name=urn:nfc:ext:nokia.com:li:id","mobileServer","*"
    push with error
    Illegall Argument java/lang/IllegalArgumentException with Invalid Parameter

    Nokia Example = not ok with device !!!!!!! OR?
    in emulator = no problem while check the 'ndef:' prefix and not more.
    Last edited by mariosas; 2007-08-08 at 21:47.

Similar Threads

  1. Autostart application and reading tag UID with one touch
    By choege in forum Near Field Communication
    Replies: 6
    Last Post: 2010-02-22, 12:38
  2. Communication between 2 Nokia 6131 NFC
    By zhs_bravo in forum Near Field Communication
    Replies: 13
    Last Post: 2009-01-05, 10:23
  3. TargetListener Problems in nokia 6131 NFC
    By JesusFD in forum Near Field Communication
    Replies: 3
    Last Post: 2008-03-31, 11:52
  4. Nokia 6131 NFC SDK 1.0 has been released
    By Nokia Ron in forum Near Field Communication
    Replies: 0
    Last Post: 2007-03-26, 22:28
  5. Can't read RFID Tag with NFC Shell
    By begermic in forum Mobile Java Tools & SDKs
    Replies: 5
    Last Post: 2007-01-31, 23:02

Posting Permissions

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