• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 52 subscribers
  • Views 369 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.

CC2540: Dynamically switching from iBeacon to Advertiseing

Michael Gonzales
Prodigy 20 points
Part Number: CC2540

I am working on an application in wich I need to switch from the iBeacon protocol to standard advertising. This needs to be done inorder to have an application on the central device (phone) wake up so it can connect to the peripheral so a connection can be established for data transfer from the peripheral.

  • 0
    TI__Mastermind 33460 points
    hello,

    iBeacon format can be treated as any other advertisement payload. You can change advertisement payloads using the
    GAPRole_SetParameter( GAPROLE_ADVERT_DATA, ...) API.
  • 0 in reply to Sean2
    Prodigy 20 points
    I’m not sure that it is that easy. There are a number of differences between iBeacon and the peripheral device we are currently advertising as. I understand that I can change the advertising payload, but changing the device from advertising non-connectible to connectible has other parameters involved.
  • 0 in reply to Michael Gonzales
    TI__Mastermind 33460 points

    Hello,

    Connectible advertisements are handled through the GAPROLE_ADVERT_ENABLED and nonconnectible are handled through the GAPROLE_ADV_NONCONN_ENABLED parameter of GAPRole_SetParameter(...).

    For more information about the peripheral gap role, I would refer to section 5.2.1 of the Software Developer's Guide that is included in the SDK. Documents folder.