The basic Problem - directed broadcast

RE: The basic Problem - directed broadcast

tesc — Wed, 22 Jun 2016 16:13:04 GMT

Sorry. There are some language difficulties. Helping with directed advertising can be difficult, since it depends on the particular phone because of address etc.

If the address that you use is correct, then the code should also be OK. In order to find out what stages works and what stages does not work:

Does everything work when you do normal advertising?

What kind of nRF device is it, is it a Development Kit? If so, does the HID Mouse example work? The HID Mouse example uses directed advertising to reconnect to the last central when the link is lost. To see that this existing example works would be a first step to getting a custom application work using the same feature.

RE: The basic Problem - directed broadcast

Sriun — Wed, 22 Jun 2016 01:44:25 GMT

I have to wonder whether your Bluetooth - directed broadcast to achieve.Because,I asked your FAE engineer,also did not give a reasonable answer;Finally, just to hit customers with problems to solve. I'm thinking about whether to continue to use your nrf51822.I was disappointed that two weeks time, a simple directed broadcast is not resolved.

RE: The basic Problem - directed broadcast

tesc — Tue, 21 Jun 2016 11:07:59 GMT

Do you have problems searching for any Bluetooth devices, or is the problem only not finding your device when it uses directed advertising?

Please provide new information here by posting comments and/or adding more information to the original question, not by starting a new question.

RE: The basic Problem - directed broadcast

Sriun — Tue, 21 Jun 2016 01:54:50 GMT

Thank you very much ,However, the problem is not resolved, the phone still can't search for Bluetooth devices.

RE: The basic Problem - directed broadcast

tesc — Mon, 20 Jun 2016 11:11:22 GMT

Hi,

You should check two things.

First, check that the byte ordering of the address is correct. addr[0] should be the least significant byte, and addr[5] should be the most significant byte. Is the address you see in the InitA field of the log correct? (Byte ordering is confusing, so it may be wrong byte ordering.)

Second, check that the address type is correct. You have chosen BLE_GAP_ADDR_TYPE_RANDOM_STATIC but the correct type may be another type. See GAP Address types.

If the phone is made by Pulsate Mobile Ltd. (company ID 0x01BE) then the address should probably be reversed and be of type BLE_GAP_ADDR_TYPE_PUBLIC. Public addresses uses the registered company ID for the two most significant bytes, see bluetooth.org for a list of company IDs.

Regards, Terje