ble_app_blinky example enable long rage and nRF Blinky APP to scan device

RE: ble_app_blinky example enable long rage and nRF Blinky APP to scan device

Tim_lai — Sun, 01 Dec 2019 11:44:17 GMT

Get it. Thanks.

RE: ble_app_blinky example enable long rage and nRF Blinky APP to scan device

MikeP — Fri, 29 Nov 2019 12:40:54 GMT

Hi Simon,

Thanks for clarification. That is fine for me, as long I can use and connect on long range. Currently we use BLE 4 in products and my initial tests are very promising. Range is one of the most important features we were looking for.

Thanks,

Mike

RE: ble_app_blinky example enable long rage and nRF Blinky APP to scan device

Simonr — Fri, 29 Nov 2019 12:33:49 GMT

Hi Tim and Mike

The reason we don't have an advertising type as you describe is that extended advertising packets (EXTENDED) do not support SCANNABLE and CONNECTABLE at the same time. This is according to the Bluetooth specification. So, because long-range advertising requires extended advertising packets we are limited to one or the other.

Best regards,

Simon

RE: ble_app_blinky example enable long rage and nRF Blinky APP to scan device

MikeP — Fri, 29 Nov 2019 11:40:39 GMT

Hi Tim,

I have just checked and I can connect in long range from S10. There is a trick that you have to click three dots next to CONNECT button in nRF Connect app, where you can select 'Connect with preferred PHY' and check LE Coded there.

Hope it helped.

RE: ble_app_blinky example enable long rage and nRF Blinky APP to scan device

MikeP — Fri, 29 Nov 2019 08:38:47 GMT

Hi Tim,

I will be playing with it over the weekend and let you know.

RE: ble_app_blinky example enable long rage and nRF Blinky APP to scan device

Tim_lai — Fri, 29 Nov 2019 02:11:46 GMT

Thanks for sharing.

You can use nRF Blinky APP to scan and connect the nRF52840 DK in long-range mode by S10?

RE: ble_app_blinky example enable long rage and nRF Blinky APP to scan device

Tim_lai — Fri, 29 Nov 2019 02:07:18 GMT

Thanks for your reply.

In my case, don't use beacon mode,

is this possible advertising type support EXTENDED, CONNECTABLE and SCANNABLE? if no, and why?

"Otherwise, you can keep using the NONSCANNABLE advertising type, but in that case, you'll have to connect to the device before going into long-range mode."

If device execute NONSCANNABLE advertising type, phone how to connect the device(nRF Blink APP can not scan to find the device and to connect)

Thanks.

RE: ble_app_blinky example enable long rage and nRF Blinky APP to scan device

MikeP — Wed, 27 Nov 2019 08:11:18 GMT

Hi, Tim,

I was playing with long range successfully. Phones compatibilty is quite awful. I have Samsung S10 which supports all BLE5.0 features and used it for testing setting blinky app to advertise on long range.

Good luck,

Mike

RE: ble_app_blinky example enable long rage and nRF Blinky APP to scan device

Simonr — Tue, 26 Nov 2019 13:47:07 GMT

Hi Tim

What phone are you using? Just because a phone/device supports BLE 5.0 doesn't mean it supports long-range (Coded_PHY). In any case, in the post you linked to, it's correct that there is no such thing as an advertising type supporting extended, connectable, and scannable advertising. So if you'd like to advertise in long-range mode, you have two options. Either you can set the advertising type to BLE_GAP_ADV_TYPE_EXTENDED_NONCONNECTABLE_SCANNABLE_UNDIRECTED. This means that the device will advertise like a beacon and will not be able to connect to your phone or any central for that matter. So, in this case, you'll have to include the data you want to be transferred in the advertising which will limit it somewhat.

Otherwise, you can keep using the NONSCANNABLE advertising type, but in that case, you'll have to connect to the device before going into long-range mode. This is described in our long-range blog post, where you connect to the central first, and goes to long-range after the connection is made so that the devices can communicate in long-range mode while being connected.

Best regards,

Simon