• State Resolved
  • Locked Locked
  • Replies 10 replies
  • Answers 1 answer
  • Subscribers 52 subscribers
  • Views 2060 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.

CC2650: how to capture multiple advertising in CC2650 Launchpad

Kaushik Chakraborty
Intellectual 795 points
Part Number: CC2650

Hi,

I want to capture multiple advertisement from a particular BLE device. I make CC2650 Launchpad as central role, along with number of Max scan responses set to 50.

I use Sensortag as device under test. Sensortag keeps on advertise in certain time period. 

My objective to see multiple advertising when i perform device discovery in CC2650 Launchpad.

can you please let me know in BTool, what are the parameters i need to set to get multiple advertising from Sensortag in CC2650 Launchpad?

Thank you

Kaushik

  • 0
    TI__Expert 5390 points

    Hi Kaushik,

    To the right section of BTool, you should be able to do this by going to the Adv Commands -> GAP -> GAP_SetParam. Then change the paramId field to TGAP_FILTER_ADV_REPORTS and set the value to 0. Finally, click on Send Command below.

    A reference screenshot is provided below:

    - Sy Su

  • 0 in reply to Sy Su
    Intellectual 795 points
    Hi Sy Su,

    I did the same. But i can't see multiple advertising get capture by CC2650 launchpad.

    Thank you.
    Kaushik
  • 0 in reply to Kaushik Chakraborty
    TI__Expert 5390 points
    Hi Kaushik,

    You are running Host Test sample application on the CC2650, correct?

    - Sy Su
  • 0 in reply to Sy Su
    Intellectual 795 points

    Hi Sy Su,

    Yes. I am using TI's Host Test Sample  Application for this.

    Thank you.

    Kaushik

  • 0 in reply to Kaushik Chakraborty
    TI__Expert 5390 points
    Hi Kaushik,

    It's possible that disabling the filter will only allow you to get multiple responses if the advertising data is different from the same advertising address. Could you try to modify the Sensortag firmware so that the advertising packet data always changes.

    -Sy Su
  • 0 in reply to Sy Su
    Intellectual 795 points

    Hi Sy Su,

    I already disable the filter.

    My sensortag always keep on sending different advertising parameters. As i embedded present humidity and temperature value in advertising packet

    But i am still not able to get multiple advertising packets in device scan of CC2650 launchpad.

    I have one more sensortag, which fw is not modified. 

    Are you saying to get multiple advertising packets from same device in one device scan, i must have different advertising packets? If so, please let me know how. as i am not manage to get it done, with my 1st sensortag.

    If we can get multiple advertising packets from same device in one device scan, where device provide a static information in advertising packet, let me know how i can get the same.

    Thank you.

    With Regards,

    kaushik

  • 0 in reply to Kaushik Chakraborty
    TI__Expert 5390 points
    Hi Kaushik,

    Could you please post your scan log that BTool produces when scanning for your device when the filter (TGAP_FILTER_ADV_REPORTS) is set to 0?

    -Sy Su
  • 0 in reply to Sy Su
    Intellectual 795 points
    Hi Sy Su,

    Please have a look into the scan log below


    [1] : <Tx> - 03:46:09.632
    -Type : 0x01 (Command)
    -OpCode : 0xFE00 (GAP_DeviceInit)
    -Data Length : 0x26 (38) byte(s)
    ProfileRole : 0x08 (8) (Central)
    MaxScanRsps : 0x14 (20)
    IRK : 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00
    CSRK : 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00
    SignCounter : 0x00000001 (1)
    Dump(Tx):
    0000:01 00 FE 26 08 14 00 00 00 00 00 00 00 00 00 00 ...&............
    0010:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
    0020:00 00 00 00 00 00 01 00 00 00 ..........
    --------------------------------------------------------------------
    [2] : <Rx> - 03:46:09.652
    -Type : 0x04 (Event)
    -EventCode : 0x00FF (Event)
    -Data Length : 0x06 (6) bytes(s)
    Event : 0x067F (1663) (GAP_HCI_ExtentionCommandStatus)
    Status : 0x00 (0) (Success)
    OpCode : 0xFE00 (GAP_DeviceInit)
    DataLength : 0x00 (0)
    Dump(Rx):
    0000:04 FF 06 7F 06 00 00 FE 00 .........
    --------------------------------------------------------------------
    [3] : <Rx> - 03:46:09.662
    -Type : 0x04 (Event)
    -EventCode : 0x00FF (Event)
    -Data Length : 0x2C (44) bytes(s)
    Event : 0x0600 (1536) (GAP_DeviceInitDone)
    Status : 0x00 (0) (Success)
    DevAddr : CC:78:AB:7F:98:80
    DataPktLen : 0x001B (27)
    NumDataPkts : 0x05 (5)
    IRK : A7:1C:40:EF:FC:10:06:5B:26:B2:2A:4F:A5:DE:0B:AF
    CSRK : BD:B9:E2:D3:8B:4A:96:7E:5B:0C:1C:76:91:15:51:FD
    Dump(Rx):
    0000:04 FF 2C 00 06 00 80 98 7F AB 78 CC 1B 00 05 A7 ..,.......x.....
    0010:1C 40 EF FC 10 06 5B 26 B2 2A 4F A5 DE 0B AF BD .@....[&.*O.....
    0020:B9 E2 D3 8B 4A 96 7E 5B 0C 1C 76 91 15 51 FD ....J.~[..v..Q.
    --------------------------------------------------------------------
    [4] : <Tx> - 03:46:23.978
    -Type : 0x01 (Command)
    -OpCode : 0xFE30 (GAP_SetParam)
    -Data Length : 0x03 (3) byte(s)
    ParamID : 0x21 (33) (TGAP_FILTER_ADV_REPORTS)
    ParamValue : 0x0000 (0)
    Dump(Tx):
    0000:01 30 FE 03 21 00 00 .0..!..
    --------------------------------------------------------------------
    [5] : <Rx> - 03:46:23.998
    -Type : 0x04 (Event)
    -EventCode : 0x00FF (Event)
    -Data Length : 0x06 (6) bytes(s)
    Event : 0x067F (1663) (GAP_HCI_ExtentionCommandStatus)
    Status : 0x00 (0) (Success)
    OpCode : 0xFE30 (GAP_SetParam)
    DataLength : 0x00 (0)
    Dump(Rx):
    0000:04 FF 06 7F 06 00 30 FE 00 ......0..
    --------------------------------------------------------------------
    [6] : <Tx> - 03:46:29.718
    -Type : 0x01 (Command)
    -OpCode : 0xFE04 (GAP_DeviceDiscoveryRequest)
    -Data Length : 0x03 (3) byte(s)
    Mode : 0x03 (3) (All)
    ActiveScan : 0x01 (1) (Enable)
    WhiteList : 0x00 (0) (Disable)
    Dump(Tx):
    0000:01 04 FE 03 03 01 00 .......
    --------------------------------------------------------------------
    [7] : <Rx> - 03:46:29.748
    -Type : 0x04 (Event)
    -EventCode : 0x00FF (Event)
    -Data Length : 0x06 (6) bytes(s)
    Event : 0x067F (1663) (GAP_HCI_ExtentionCommandStatus)
    Status : 0x00 (0) (Success)
    OpCode : 0xFE04 (GAP_DeviceDiscoveryRequest)
    DataLength : 0x00 (0)
    Dump(Rx):
    0000:04 FF 06 7F 06 00 04 FE 00 .........
    --------------------------------------------------------------------
    [8] : <Rx> - 03:46:29.818
    -Type : 0x04 (Event)
    -EventCode : 0x00FF (Event)
    -Data Length : 0x2C (44) bytes(s)
    Event : 0x060D (1549) (GAP_DeviceInformation)
    Status : 0x00 (0) (Success)
    EventType : 0x00 (0) (Connectable Undirect Advertisement)
    AddrType : 0x00 (0) (Public)
    Addr : 24:71:89:E8:55:86
    Rssi : 0xD9 (217)
    DataLength : 0x1F (31)
    Data : 02:01:06:03:02:80:AA:17:FF:48:75:6D:69:64:69:74:79:3D:20:D0:75:54:65:6D:70:3D:20:BC:65:00:00
    Dump(Rx):
    0000:04 FF 2C 0D 06 00 00 00 86 55 E8 89 71 24 D9 1F ..,......U..q$..
    0010:02 01 06 03 02 80 AA 17 FF 48 75 6D 69 64 69 74 .........Humidit
    0020:79 3D 20 D0 75 54 65 6D 70 3D 20 BC 65 00 00 y= .uTemp= .e..
    --------------------------------------------------------------------
    [9] : <Rx> - 03:46:29.848
    -Type : 0x04 (Event)
    -EventCode : 0x00FF (Event)
    -Data Length : 0x28 (40) bytes(s)
    Event : 0x060D (1549) (GAP_DeviceInformation)
    Status : 0x00 (0) (Success)
    EventType : 0x04 (4) (Scan Response)
    AddrType : 0x00 (0) (Public)
    Addr : 24:71:89:E8:55:86
    Rssi : 0xD9 (217)
    DataLength : 0x1B (27)
    Data : 11:09:43:43:32:36:35:30:20:53:65:6E:73:6F:72:54:61:67:05:12:08:00:20:03:02:0A:00
    Dump(Rx):
    0000:04 FF 28 0D 06 00 04 00 86 55 E8 89 71 24 D9 1B ..(......U..q$..
    0010:11 09 43 43 32 36 35 30 20 53 65 6E 73 6F 72 54 ..CC2650 SensorT
    0020:61 67 05 12 08 00 20 03 02 0A 00 ag.... ....
    --------------------------------------------------------------------
    [10] : <Rx> - 03:46:29.988
    -Type : 0x04 (Event)
    -EventCode : 0x00FF (Event)
    -Data Length : 0x2B (43) bytes(s)
    Event : 0x060D (1549) (GAP_DeviceInformation)
    Status : 0x00 (0) (Success)
    EventType : 0x00 (0) (Connectable Undirect Advertisement)
    AddrType : 0x00 (0) (Public)
    Addr : 00:A0:50:43:05:75
    Rssi : 0xB3 (179)
    DataLength : 0x1E (30)
    Data : 02:01:06:1A:FF:4C:00:02:15:77:05:24:62:73:ED:49:BF:BD:1D:8F:68:95:6C:4A:D9:00:01:00:01:2D
    Dump(Rx):
    0000:04 FF 2B 0D 06 00 00 00 75 05 43 50 A0 00 B3 1E ..+.....u.CP....
    0010:02 01 06 1A FF 4C 00 02 15 77 05 24 62 73 ED 49 .....L...w.$bs.I
    0020:BF BD 1D 8F 68 95 6C 4A D9 00 01 00 01 2D ....h.lJ.....-
    --------------------------------------------------------------------
    [11] : <Rx> - 03:46:30.008
    -Type : 0x04 (Event)
    -EventCode : 0x00FF (Event)
    -Data Length : 0x2C (44) bytes(s)
    Event : 0x060D (1549) (GAP_DeviceInformation)
    Status : 0x00 (0) (Success)
    EventType : 0x04 (4) (Scan Response)
    AddrType : 0x00 (0) (Public)
    Addr : 00:A0:50:43:05:75
    Rssi : 0xB3 (179)
    DataLength : 0x1F (31)
    Data : 0C:09:53:65:6E:73:65:50:65:61:6E:75:74:11:06:43:1F:51:03:9E:3A:67:87:57:47:D0:58:E1:3C:CD:93
    Dump(Rx):
    0000:04 FF 2C 0D 06 00 04 00 75 05 43 50 A0 00 B3 1F ..,.....u.CP....
    0010:0C 09 53 65 6E 73 65 50 65 61 6E 75 74 11 06 43 ..SensePeanut..C
    0020:1F 51 03 9E 3A 67 87 57 47 D0 58 E1 3C CD 93 .Q..:g.WG.X.<..
    --------------------------------------------------------------------
    [12] : <Rx> - 03:46:39.986
    -Type : 0x04 (Event)
    -EventCode : 0x00FF (Event)
    -Data Length : 0x14 (20) bytes(s)
    Event : 0x0601 (1537) (GAP_DeviceDiscoveryDone)
    Status : 0x00 (0) (Success)
    NumDevs : 0x02 (2)
    Device #0
    EventType : 0x00 (0) (Connectable Undirect Advertisement)
    AddrType : 0x00 (0) (Public)
    Addr : 24:71:89:E8:55:86
    Device #1
    EventType : 0x00 (0) (Connectable Undirect Advertisement)
    AddrType : 0x00 (0) (Public)
    Addr : 00:A0:50:43:05:75
    Dump(Rx):
    0000:04 FF 14 01 06 00 02 00 00 86 55 E8 89 71 24 00 ..........U..q$.
    0010:00 75 05 43 50 A0 00 .u.CP..
    --------------------------------------------------------------------



    Thank you.
    WIth Regards,
    Kaushik
  • 0 in reply to Kaushik Chakraborty
    TI__Expert 5390 points

    Hi Kaushik,

    Based on your log, it looks like you're using an older version of BTool that had a bug where the GAP_SetParam was sending the command value to the incorrect command. This has since been fixed in the newer versions of BTool.
    To access this, download the most recent CC2650 SDK at http://www.ti.com/tool/ble-stack and use the version BTool available within the SDK.

    Also to clarify, you will not need to change the advertisement data.

    -Sy Su

  • 0 in reply to Sy Su
    Intellectual 795 points
    Hi Sy Su,

    Thanks a lot. It work perfectly.

    Thank you.
    With Regards,
    Kaushik