Raw Data

RE: Raw Data

Aleksander Nowakowski — Thu, 14 May 2020 10:05:20 GMT

BLE APP UART does not set Manufacturer Data in `gap_params_init`. but e.g. ble_app_beacon sample does set advdata.p_manuf_specific_data, which is then passed to ble_advdata_encode. This encode method encodes the advertising data to use AD types.

RE: Raw Data

Manoj Hiwarkar — Thu, 14 May 2020 09:05:17 GMT

Automatically means? somewhere it mus be calculating.

RE: Raw Data

Aleksander Nowakowski — Thu, 14 May 2020 04:54:25 GMT

When you set the manufacturer data, the 0x1A is there length of the data and 0xFF is the Manufacturer Data Type. So it's set automatically when settin asking manufacturer data to the adv packet.

RE: Raw Data

Manoj Hiwarkar — Wed, 13 May 2020 21:01:41 GMT

where are these values 0x1AFF set in the code of BLE APP UART ?

RE: Raw Data

Manoj Hiwarkar — Tue, 05 May 2020 15:23:16 GMT

can you please respond ? its urgent.

RE: Raw Data

Manoj Hiwarkar — Tue, 05 May 2020 15:07:36 GMT

OK is it possible to flags atleast using nrf52 ? How? pl reply.

RE: Raw Data

Manoj Hiwarkar — Tue, 05 May 2020 14:48:42 GMT

sorry i wanted to say that I am not advertising it "from" the phone,I am advertising it "to" or "on" the phone.

RE: Raw Data

Kenneth — Tue, 05 May 2020 14:46:17 GMT

You may also check out the documentation by silabs in this case, in short it is not possible to replace the data no:
https://www.silabs.com/community/wireless/bluetooth/knowledge-base.entry.html/2017/02/10/bluetooth_advertisin-hGsf

You may consider using scan response packet if you need more data to be advertised.

RE: Raw Data

Aleksander Nowakowski — Tue, 05 May 2020 14:45:56 GMT

First, you wrote:

> I am advertising the data on android phone and my device is Nrf52.

Which I understand, that the phone has Peripheral Role, and your nRF52 is a Central (scans).

Now, you write:

> I am advertising it "from" the phone., I am advertising it "to" the phone

Which is missing "not", but I don't know where.

RE: Raw Data

Manoj Hiwarkar — Tue, 05 May 2020 14:42:00 GMT

I haven't understood what you want to say and I am advertising it "from" the phone., I am advertising it "to" the phone

RE: Raw Data

Aleksander Nowakowski — Tue, 05 May 2020 14:38:42 GMT

The advertising packet has nothing in common with characteristics. A characteristic may have any value you want. When it comes to advertising packet, you need to use AD and SRD (described above) data types, which have syntax described above.

When you advertise from a phone, you cannot remove or change those 5 bytes. You may use Scan Response, which can contain additional 31 bytes (of those at least 2 will be used for Length and Type of another, possible again Manufacturer Data, data type.

RE: Raw Data

Manoj Hiwarkar — Tue, 05 May 2020 14:33:32 GMT

I have to implement the custom characteristics which have a different 31 byte packet format.These five bytes are taking the space which I want to replace by some other data.Is that possble. I am advertising the data on android phone and my device is Nrf52. Tell me at least how to change the value of those bytes.

RE: Raw Data

Aleksander Nowakowski — Tue, 05 May 2020 14:29:08 GMT

If you're advertising from a device where you can control the advertising packet, like a nRF5 device, you may remove flags, so you will remove 0x020104. But 0x1AFF must be there in order the Manufacturer Data be decoded correctly. If you are using some other device, like a mobile phone, you cannot remove flags, as they are managed by the system. Also, I don't know if you should remove flags. Each flag has its meaning and they aren't there just to take 3 bytes.

RE: Raw Data

Manoj Hiwarkar — Tue, 05 May 2020 14:20:06 GMT

can I remove 0201041AFF or not ?

RE: Raw Data

Aleksander Nowakowski — Tue, 05 May 2020 12:21:14 GMT

Hello,

The advertising packet and scan response data are built using LTV (Length-Type-Value) format (similar to TLV, but Length comes first).

You may read more in Core Bluetooth specification 5.2, Vol 3, Part C, Chapter 11, Supplement to the Bluetooth Core Specification (the same link), chapter 1. The IDs of available types are listed here: https://www.bluetooth.com/specifications/assigned-numbers/generic-access-profile/

Each entry starts with Length, in bytes, of the following type + data. Length of type is always 1 (can be extended in the future).

The raw data you scanned: 0x0201041AFF590000150112233445566778899AABBCCDDEEFF0FFFFFFFFC3 are split into entries the following way (nRF Connect for Android also displays this in the table below the raw data):

Len Type. Value
0x02 0x01 (Flags) 0x04 - BR/EDR Not Supported
0x1A. 0xFF (Manufacturer Data) 0x59000000150112233445566778899AABBCCDDEEFF0FFFFFFFFC3

The Supplement to Bluetooth Core Specification 4.1+ defines the first 2 bytes of Manufacturer data as Company ID.

The Manufacturer Data are encoded using application format, in this case nRF Beacon format, or something similar.

0x5900 - Nordic Semiconductor ASA Company ID (https://www.bluetooth.com/specifications/assigned-numbers/company-identifiers/), in Little Endian
0x00 - beacon type - this should be 0x02, actually
0x15 - length of the rest of payload
0x0112233445566778899AABBCCDDEEFF0 - the UUID: 01122334-4556-6778-899A-ABBCCDDEEFF0
0xFFFF - major number
0xFFFF - minor number
0xC3 - the calculated RSSI signal at 1m, in dBm = -61 dBm

RE: Raw Data

Manoj Hiwarkar — Tue, 05 May 2020 08:58:17 GMT

is anyone here to respond?