The manufacturer specific data is a part of the advertising string, so the suggested tutorial should be taken as reference. In step #1 there is an example demonstrating how to set the adv data.
The GAP Advertising Data Types, as defined by Bluetooth Core specification can be found in gap_data_type_t structure in ble_gap.h.
The GAP_DATA_TYPE_MANUFACTURER_SPEC should be used for the Manufacturer Specific Data. Again you should follow the concept from the GAP_DATA_TYPE_LOCAL_NAME. Additionally the ble_gap_adv_data_set() should be used in order to set either the adv or scan response data.
Hi,
please check this Tutorial:
http://lpccs-docs.dialog-semiconductor.com/da1468x_advertising_concept/c...
BR, Paolo
hello Dialog,
thank you for your Answer,
when i´m debugging the code I have seen manufaturer specific data in advertsising data of ble in ble scanner app.
The Link that you sharing me talk about the Adversting Data and i want to write my custoom Data in the manufaturer specific data.
the Data format look like this:
Result = 1604937913613 ScanResult{device=80:EA:CA:80:00:01,
scanRecord=ScanRecord [mAdvertiseFlags=6,
mServiceUuids = [00002 ea7 - 0000 - 1000 - 8000 - 00805f9b34fb,
0000180f-0000-1000-8000-00805f9b34fb,
0000c8c5-0000-1000-8000-00805f9b34fb,
0000180d-0000-1000-8000-00805f9b34fb,
0000fef5-0000-1000-8000-00805f9b34fb],
mServiceSolicitationUuids=[],
mManufacturerSpecificData={210=[-128, 0, 1]},
mServiceData={},
mTxPowerLevel=-2147483648,
mDeviceName=Dialog WRBL],
rssi=-62,
timestampNanos=18950393039360,
eventType=27,
primaryPhy=1,
secondaryPhy=0,
advertisingSid=255,
txPower=127,
periodicAdvertisingInterval=0}
thank you
Lionel03
Hello Dialog,
i want to fill this mManufacturerSpecificData={210=[-128, 0, 1]} with my customer Data. and what is the manufacturerId?
Thank you
Lionel03
Hi Lionel03,
The manufacturer specific data is a part of the advertising string, so the suggested tutorial should be taken as reference. In step #1 there is an example demonstrating how to set the adv data.
The GAP Advertising Data Types, as defined by Bluetooth Core specification can be found in gap_data_type_t structure in ble_gap.h.
The GAP_DATA_TYPE_MANUFACTURER_SPEC should be used for the Manufacturer Specific Data. Again you should follow the concept from the GAP_DATA_TYPE_LOCAL_NAME. Additionally the ble_gap_adv_data_set() should be used in order to set either the adv or scan response data.
Please see an example below :
Thanks, PM_Dialog