This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

nrf connect SDK coded PHY nrf52833/20

Hi All! 

I am using nrf52833/20DK. I have a few general questions regarding the nrf connect SDK.

1)nrf connect sdk supports connectable coded PHY advertisement? if yes can you please mention the example with the SDK version?

2)Is there any example in nrf52 SDK OR nrf connect SDK that supports coded PHY beacons with ACK to sender? This means if a packet/beacon is sent to the receiver then it will send back the ACK to the sender to ensure at the sender's end that the message is received.

3)How many coded PHY concurrent connections can support nrf connect sdk & nrf52 SDK?Nimble mentioned that it supports 32 concurrent connections as mentioned in the link

https://mynewt.apache.org/

Thanks in Advance!

Parents
  • Hi,

    1) See the Bluetooth: Peripheral Heart Rate Monitor with Coded PHY example. It advertises and connects using Coded PHY.

    2) Advertisements do not produce ACKs back to the sender. This is by Bluetooth specification. There are two ways a scanner can send packets back to an advertiser:

    • One is if doing active scanning, where scannable advertisements will trigger a scan request from the scanner. However I am not aware of any hooks onto this where you can know on the advertiser side which scanner has sent a scan request.
    • The other is if doing connectable advertising, where the scanner (acting as initiator) may send a connection request.

    3) nRF5 SDK (using the SoftDevice) and nRF Connect SDK using the SoftDevice Controller has a maximum of 20 concurrent links.

    Please note that we are entering Easter vacation in Norway. You may have to wait until next week for answers to any follow-up questions.

    Regards,
    Terje

  • Hi tesc

    Thank you for the answer!

    1)I am using sdk 17.0.1 / 17.1.2 . nrf board is nrf52833sdk and example i am following is 

    ble_app_blinky & ble_app_blinky_c .

    As you can see in the following image option available is having a default value of 1 for central and the link count for peripheral is 0. How can we set it to 20? for both the central and link count we have to set it to 20 and set peripheral and 0? 

    2)For nrf connect sdk v1.9.1 using peripheral_hr_coded example. Can you please help me where is the configuration to set the concurrent connection value?

    3)We are using nrf52833/20 or nrf52840 sdk for the development what do you suggest me to start with nrf52 sdk or nrf connect sdk ? Because some people said that nrf52 is best for the 52 devices and some suggest nrf connnect sdk.

    Thanks in advance!

  • Hi,

    First of all I am sorry for the long wait.

    1) You should set total link count to 20, central link count to 20, and peripheral link count to 0, yes.

    2) If you mean a setting for number of links, then the same settings as in 1) are needed for the SoftDevice to support the number of connections. In addition you may need code changes. Some examples connect to one device, then doesn't start any new advertising afterwards (such as e.g. the HID examples.) Other examples have concurrent connections, so they start advertising again after a connection has been set up (as long as there is room for more connections.) This happens for instance in the BLE Multi-link Example.

    3) The answers above are for nRF5 SDK. For new projects, we recommend using nRF Connect SDK, also for the nRF52 series. New development will happen in nRF Connect SDK, while the (older) nRF5 SDK is in maintenance mode. See our statement on nRF Connect SDK and nRF5 SDK.

    Regards,
    Terje

Reply
  • Hi,

    First of all I am sorry for the long wait.

    1) You should set total link count to 20, central link count to 20, and peripheral link count to 0, yes.

    2) If you mean a setting for number of links, then the same settings as in 1) are needed for the SoftDevice to support the number of connections. In addition you may need code changes. Some examples connect to one device, then doesn't start any new advertising afterwards (such as e.g. the HID examples.) Other examples have concurrent connections, so they start advertising again after a connection has been set up (as long as there is room for more connections.) This happens for instance in the BLE Multi-link Example.

    3) The answers above are for nRF5 SDK. For new projects, we recommend using nRF Connect SDK, also for the nRF52 series. New development will happen in nRF Connect SDK, while the (older) nRF5 SDK is in maintenance mode. See our statement on nRF Connect SDK and nRF5 SDK.

    Regards,
    Terje

Children
Related