i am using the observer example but i am not seeing any advertising packet manufacturing data

Hi,

I am using the observer example which is quite good but i also want to see the manufacturing data of the advertising packet, i tried adding the buf->data for the net_buf_simple data type but this is not giving me what i would expect. below is the data i received:

[DEVICE]: 58:7B:5B:46:0B:41 (random), AD evt type 0, Tx Pwr: 127, RSSI -41 Data status: 0, AD data len: 31 Name: William's S21 C:1 S:1 D:0 SR:0 E:0 Pri PHY: LE 1M, Sec PHY: No packets, Interval: 0x0000 (0 ms), SID: 255, buf data 536901229

is there a way to print the advertising data manufacturing data?

thanks,

William

Parents
  • Hi Karl,

    Do i perhaps need to enable some form of filter or advanced advertising to collect the manufacturing data?

    is there any chance there is an example of manufacture data collection? i have not been able to find any,

    Regards,

    William

  • Hello William,

    WilliamMcCoy21 said:
    Do i perhaps need to enable some form of filter or advanced advertising to collect the manufacturing data?

    You do not need a specific filter for this, no - using the bt_data_parse function with a case for the BT_DATA_MANUFACTURER_DATA will return manufacturer specific data so long as that datafield is populated in the advertising.

    With the code you are currently using you are parsing the data in the scan response, but not as part of your device_found (which happens after a filter match).

    WilliamMcCoy21 said:
    is there any chance there is an example of manufacture data collection? i have not been able to find any,

    I dont know of any such example unfortunately, but I could make you a minimal one tomorrow to highlight how you can get a hold of this information if you would like.

    Best regards,
    Karl

  • Hi Karl,

    Thank you for your help, i tried using another device as the advertiser, using the beacon example on another nrf52840 DK i can now see the manufacturing data, it appears that my phone was not transmitting the data as i expected,

    Thank you,

    William

  • Hello William,

    WilliamMcCoy21 said:
    Thank you for your help

    No problem at all, I am happy to help! :) 

    WilliamMcCoy21 said:
    i tried using another device as the advertiser, using the beacon example on another nrf52840 DK i can now see the manufacturing data, it appears that my phone was not transmitting the data as i expected,

    I am glad to read that you were able to use the bt_data_parse function to extract the manufacturer specific data after all! 
    It does sound strange to me that the advertising of the nRF Connect SDK BLE application did not look as expected - I will make a short test to check what might have happened here, and relay the results to our developers if I find something wrong. Thank you for the update! :) 

    Best regards,
    Karl

  • Hello again, William

    I just wanted to let you know that I attempted to replicate the behavior you reported by using the nRF Connect for Smartphones application to set up an advertiser with the manufacturer specific datafield, and then use the nRF Sniffer tool to verify that the advertising was correctly populated.
    In my test everything behaved as expected, and so the manufacturer specific datafield was present and populated with the data input to the nRF Connect for Smartphone application.

    Do you have any additional information or steps that I could take to reproduce?
    If not then I will close this ticket since your original issue has been resolved (but you can of course always open another ticket in the future if you should have any other questions!).

    Best regards,
    Karl

Reply
  • Hello again, William

    I just wanted to let you know that I attempted to replicate the behavior you reported by using the nRF Connect for Smartphones application to set up an advertiser with the manufacturer specific datafield, and then use the nRF Sniffer tool to verify that the advertising was correctly populated.
    In my test everything behaved as expected, and so the manufacturer specific datafield was present and populated with the data input to the nRF Connect for Smartphone application.

    Do you have any additional information or steps that I could take to reproduce?
    If not then I will close this ticket since your original issue has been resolved (but you can of course always open another ticket in the future if you should have any other questions!).

    Best regards,
    Karl

Children
No Data
Related