This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

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

Hi All,

I study this post to enable long-range(s=8) on ble_app_blinky (nRF5_SDK_16.0.0_98a08e2\examples\ble_peripheral\ble_app_blinky)

In the post, one of the settings is set adv_params.properties.type = BLE_GAP_ADV_TYPE_EXTENDED_CONNECTABLE_NONSCANNABLE_UNDIRECTED;

I can not scan the nRF52840 DK if I use nRF Blinky APP on phone(support BLE5.0).

Can not scan the DK because the adv_params.properties.type for NONSCANNABLE?

Is this possible ble_app_blinky with long-range(S=8) and utilize nRF Blinky APP to control?

Thanks,

Tim

Parents
  • 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

Reply
  • 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

Children
  • 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.

Related