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

Hi, Do the S140 version 6.1.1 SoftDevice does have full support for S=2(500 kbps) ?

if yes how can i choose between S=2 and S=8, where the change should take place, at the advertising init ?

Parents Reply Children
  • Hi.

    I can't compile neither of these projects, and I don't see that you have called sd_ble_gap_adv_set_configure() in either one of them.

    Best regards,

    Andreas

  • Hi,

    thanks for your reply

    in order to compile these projects you need to add them to the SDK 15.2 as the other examples.

    the function : sd_ble_gap_adv_set_configure() is called by ble_advertising_init() that called by the advertising_init() in main.c

    I appreciate your help

    Best regards

    Jawad

  • Hi.

    I was able to compile the projects in SDK 15.0, and debug them. But I did not get any errors, here is my output:

    Central:

    <info> app: BLE UART central example started.
    <info> app: ADV. report
    <info> app: ADV. report
    <info> app: ADV. report
    <info> app: ADV. report
    <info> app: ADV. report
    <info> app: ADV. report
    <info> app: ADV. report
    <info> app: Connecting to target 914819FB65EE
    <info> app: Connected to target
    <info> app: RSSI : -35 dBm
    <info> app: ATT MTU exchange completed.
    <info> app: Ble NUS max data length set to 0xF4(244)
    <info> app: Discovery complete.
    <info> app: Connected to device with Nordic UART Service.
    <info> app: RSSI : -25 dBm
    <info> app: RSSI : -36 dBm
    <info> app: RSSI : -26 dBm
    <info> app: Disconnected.
    <info> app: ADV. report
    <info> app: ADV. report
    <info> app: Connecting to target 914819FB65EE
    <info> app: Connected to target
    <info> app: RSSI : -24 dBm
    <info> app: ATT MTU exchange completed.
    <info> app: Ble NUS max data length set to 0xF4(244)
    <info> app: Discovery complete.
    <info> app: Connected to device with Nordic UART Service.
    

    Peripheral:

    <info> app: Debug logging for UART over RTT started.
    <info> app: Connected
    <info> app: Data len is set to 0xF4(244)
    <info> app: Debug logging for UART over RTT started.
    <info> app: Connected
    <info> app: Data len is set to 0xF4(244)
    

    Is the problem still NRF_ERROR_INVALID_PARAM? I'm a bit unsure what the problem is now.

    Best regards,

    Andreas

  • Hi , now there is no problem regards the range I get after testing Long Range

    In long range I got 75 meter range between two ntf52840 ...

    In normal with BLE_GAP_PHY_1MBPS I got the same range ( 75 meters )

    Is there any problem with the code ?

    Regards

    Jawad K

  • Hi.

    I don't think you have configured the PHY correctly then. Can you use a sniffer to sniff for BLE packets? They should be marked with CODED_PHY if they are CODED_PHY.

    The worst case range you should expect in open air is atleast double distance from BLE_GAP_PHY_1MBPS

    Best regards,

    Andreas

Related