Long range with SDK16.0.0

RE: Long range with SDK16.0.0

Steven983 — Tue, 18 Feb 2020 23:49:09 GMT

I still have one more question. In the Uart example, the structure of ble_advertising_init_t is used to initiate the advertising module. However, the stucture of ble_gap_adv_params_t is used in the blinky example. What is the difference between these two types of structure? And how to choose them in different situations?

RE: Long range with SDK16.0.0

Steven983 — Tue, 18 Feb 2020 23:45:14 GMT

It works. Thanks Simon.

RE: Long range with SDK16.0.0

Simonr — Mon, 20 Jan 2020 13:18:10 GMT

Can you try to enable authorization for read/write of the characteristic that returns error code 0x0007? That error code means that there's an insufficient encryption key size somewhere.

I suggest you check out the project I uploaded and see if you can find anything that differs from your project as well, as that project is confirmed to work from our end.

Best regards,

Simon

RE: Long range with SDK16.0.0

Steven983 — Sun, 19 Jan 2020 22:15:57 GMT

Hi Simon,

It doesn't work after I set adv_data.p_data to NULL. The reson that I didn't add the payload in the scan response is that in this Blog post https://devzone.nordicsemi.com/f/nordic-q-a/38267/long-range/183279#183279, Harvard said that srdata (scan response data) is not used together with extended advertising, and should not be encoded and suggeted that srdata should set to NULL.

Any more advice?

Best,

Steven

RE: Long range with SDK16.0.0

Simonr — Fri, 17 Jan 2020 13:41:29 GMT

I see that you haven't added the payload in the scan response. Can you try setting adv_data.p_data to NULL? You can use this project as a template for how a Coded PHY example should be set up for advertising, as not much has changed in that regard since SDK v.15.2.

devzone.nordicsemi.com/.../nRF5_5F00_SDK_5F00_15.2.0_5F00_mod.zip

Best regards,

Simon