• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 17 subscribers
  • Views 4596 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

NDEF message maker usage for more than one NDEF record

Michael Qian
Intellectual 2380 points
Other Parts Discussed in Thread: RF430CL330H

Hi all,

I know we have one tool to make NDEF record into RC430CL330, but I have puzzle about how to make a message with two or more record with NDEF message maker we have.

Do some one could help on this? Or how could I add two or more NDEF records by this tool and make them into one NDEF message?

I am headache with the NFC forum specification NFCForum-TS-RTD_1.0 describtion.

  • 0
    TI__Mastermind 26420 points

    Hey Michael,

    I know Eddie has created an NDEF message with multiple records.  I'll ping him for you, and have him let you in on his secrets.  I don't think the tool can do it, as is.   

    Thanks,

    JD

  • 0
    TI__Mastermind 38590 points

    Hi Michael,

    The NDEF maker does not allow for this natively, but you can just create two records and pretty easily merge them together with a couple changes.  See the attached BT handover + URI records attached and steps below. 

    You need to refer to the NFC Forum NDEF specification for the record header format requirements.  Here are the steps I took to merge two records together. 

    1.  Create both records(BT_pair.txt & URI.txt).

    2. Decide which record will be first.  In this example, I made the BT pair record first. 

    3. Add second record to BT_pair.  You only need to have the record data which starts with the record header. 

    4. NLEN must now be changed to reflect the size of both records.  In this case, 70 + 11 = 81 bytes (0x51).  NLEN is located right after the NDEF File ID

    5. Record headers must now be changed to reflect the message begin(MB) and message end(ME).  See the record layout in the NDEF specification for details.  I also included the layout below.  If more than 2 messages are used, the middle messages should have both MB and ME set to 0.

    Let me know if you have other questions.

    NDEF_Merge.zip
  • 0 in reply to Eddie LaCost
    TI__Intellectual 2380 points

    Eddie,

    It's cool. Thanks for your explain, gradually I get your point:

    NDEF tag application,  CC ID, CC file and NDEF ID are the definition of an NDEF tag.

    It has many information of tag, from NLEN is related to record, and NDEF header byte definition begins to manage so many records.

    One more question is that wifi pair seems hard to connected. it couldn't connected to android wifi automatic like bluetooth pairing.

    I am planing to make bluetooth and wifi record into one NDEF message, to use to connect to smartphone wifi and Bluetooth automatic when smartphone touch the RF430CL330 once.

  • 0 in reply to Michael Qian
    TI__Mastermind 38590 points

    Michael,

    You are on the right track now with your understanding of NDEF.  You are correct that the WiFi pairing has not yet been implemented in the Android OS.  For now, you can install a background application called "Wifi Tap" from the Play store.  This application just needs to be installed on the phone and when it reads the NDEF record with this particular formatting, it will attempt to connect to that SSID using the given security key.

  • 0 in reply to Eddie LaCost
    Prodigy 230 points

    Hey, hello!

    Sorry to bring back this post, but I have some doubts about NDEF messages in RF430CL330H. I played a lot with TI's NDEF Maker (v1.08) and following Eddie instructions, I also created this double record tag (BT + URL). My (dumb) question is: should my smartphone pop-up both BT pairing and browser with the URL? I'm only getting BT one (but there're two records, as NXP app says).

    Also, I'd like to ask if there's a way to include BT's PIN in NDEF. I read somewhere these bytes were removed (old Nokia specification), but the sphone should try the default one (0000, ou 1234). Is that true?

    Thanks, and sorry again!

  • 0 in reply to Pedro
    TI__Mastermind 38590 points

    Hi Pedro,

    I beleive that you would need to have your own application to be able to handle multiple records in a single NDEF.  You can also add another AAR record so that specific app is used or directs the user to the play store to download if it is not already installed.

    You can find the latest specification below.  There is no field available for PIN.  See the example in table 10.

    http://nfc-forum.org/our-work/specifications-and-application-documents/application-documents/

  • 0 in reply to Eddie LaCost
    Prodigy 230 points

    Hello Eddie, thanks for the information!

    I'll try to rewrite my Android app!

    Thanks!