• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 52 subscribers
  • Views 1475 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

SIMPLELINK-CC2640R2-SDK: SDK v1.50: Simple Broadcaster Beacon not detected at Smart Phone App?

Markel Robregado
Guru 86865 points

Part Number: SIMPLELINK-CC2640R2-SDK
Other Parts Discussed in Thread: BLE-STACK

Hi,

    I set the BEACON_FEATURE predefine at Simple Broadcaster example program to make device function as a Beacon. But using eBeacon IOS App I am not able to see it at Eddystone Tab. Is there anything else I need to do in order for the Simple Broadcaster example program to function as Eddystone Beacon?

-kel

  • 0
    TI__Guru 56590 points
    Hello Markel,
    Did you try the micro_eddystone_beacon example code from simplelink_cc2640r2_sdk_1_50_00_58?
    Have you reviewed the app note: Implementing Eddystone Bluetooth Smart Beacons Using the TI BLE-Stack?
  • 0 in reply to Eirik V
    Guru 86865 points
    Hi Eirik,

    I have tried the micro_eddystone_beacon example program several times and it works. I see it at eBeacon->Eddystone Tab. However, as I have mentioned above using Simple Broadcaster example program and with BEACON_FEATURE predefine set I am unable to see it at eBeacon->Eddystone Tab.

    -kel
  • 0 in reply to Markel Robregado
    TI__Guru 57865 points

    Hi Markel,
    Can you verify the packet content being sent OTA? What packet format do you expect?

    I checked the sample app, and the BEACON_FEATURE is setting up hardcoded iBeacon packet (not eddystone). Does the eBeacon app support that?

  • 0 in reply to J Lindh
    Guru 86865 points

    Hi Joakim,

        I do not have a Packet Analyzer to check. I want a Eddystone packet, because my end objective is a Connectable Eddystone Beacon. I thought of copying the advertisement data from Simple Broadcaster to Simple Peripheral.

        At Simple Broadcaster with BEACON_FEATURE nothing appears at eBeacon->iBeacon and eBeacon->Eddystone tab. However using micro eddystone beacon I see this below at eBeacon->Eddystone tab after pressing Button 2. I also used Beacon Manager App for testing and same results.

    -kel

  • 0 in reply to Markel Robregado
    TI__Guru 57865 points

    Markel,

    Eddystone and iBeacon are two completely different packet formats and they are not compatible. In order to send Eddystone packets from the Simple Broadcaster, you will need to update the content of the advertised data. The specific code you will need to update is

      // 25 byte beacon advertisement data
  // Preamble: Company ID - 0x000D for TI, refer to www.bluetooth.org/.../company-identifiers
  // Data type: Beacon (0x02)
  // Data length: 0x15
  // UUID: 00000000-0000-0000-0000-000000000000 (null beacon)
  // Major: 1 (0x0001)
  // Minor: 1 (0x0001)
  // Measured Power: -59 (0xc5)
  0x1A, // length of this data including the data type byte
  GAP_ADTYPE_MANUFACTURER_SPECIFIC, // manufacturer specific adv data type
  0x0D, // Company ID - Fixed
  0x00, // Company ID - Fixed
  0x02, // Data Type - Fixed
  0x15, // Data Length - Fixed
  0x00, // UUID - Variable based on different use cases/applications
  0x00, // UUID
  0x00, // UUID
  0x00, // UUID
  0x00, // UUID
  0x00, // UUID
  0x00, // UUID
  0x00, // UUID
  0x00, // UUID
  0x00, // UUID
  0x00, // UUID
  0x00, // UUID
  0x00, // UUID
  0x00, // UUID
  0x00, // UUID
  0x00, // UUID
  0x00, // Major
  0x01, // Major
  0x00, // Minor
  0x01, // Minor
  0xc5  // Power - The 2's complement of the calibrated Tx Power

     If you are looking to support all various Eddystone beacon modes, you might have to port some of the logic as well.

  • 0 in reply to J Lindh
    Guru 86865 points
    Thanks. I will learn from the micro eddystone example program.